1
0
mirror of https://github.com/postgres/postgres.git synced 2025-05-26 18:17:33 +03:00

doc: Fix INSERT statement syntax for identity columns

The INSERT statements in the examples were erroneously using
VALUE instead of VALUES. Backpatch to v17 where the examples
were added through a37bb7c1399.

Reported-by: shixiong327926@gmail.com
Discussion: https://postgr.es/m/172958472112.696.6075270400394560263@wrigleys.postgresql.org
Backpatch-through: 17
This commit is contained in:
Daniel Gustafsson 2024-10-23 14:58:17 +02:00
parent f92f6b3db4
commit 0a059206fc

View File

@ -271,8 +271,8 @@ CREATE TABLE people (
example, with the above definitions and assuming additional appropriate
columns, writing
<programlisting>
INSERT INTO people (name, address) VALUE ('A', 'foo');
INSERT INTO people (name, address) VALUE ('B', 'bar');
INSERT INTO people (name, address) VALUES ('A', 'foo');
INSERT INTO people (name, address) VALUES ('B', 'bar');
</programlisting>
would generate values for the <literal>id</literal> column starting at 1
and result in the following table data:
@ -285,7 +285,7 @@ INSERT INTO people (name, address) VALUE ('B', 'bar');
Alternatively, the keyword <literal>DEFAULT</literal> can be specified in
place of a value to explicitly request the sequence-generated value, like
<programlisting>
INSERT INTO people (id, name, address) VALUE (<emphasis>DEFAULT</emphasis>, 'C', 'baz');
INSERT INTO people (id, name, address) VALUES (<emphasis>DEFAULT</emphasis>, 'C', 'baz');
</programlisting>
Similarly, the keyword <literal>DEFAULT</literal> can be used in
<command>UPDATE</command> commands.