Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit e38217d

Browse files
committed
Improve constraint_name wording.
1 parent a0ae3db commit e38217d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/src/sgml/ref/create_table.sgml

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.98 2006/01/16 19:53:12 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.99 2006/01/16 20:48:49 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -295,10 +295,10 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
295295
<para>
296296
An optional name for a column or table constraint. If the
297297
constraint is violated, the constraint name is present in error messages,
298-
so constraint names like <literal>"col must be positive"</> can be used
298+
so constraint names like <literal>col must be positive</> can be used
299299
to communicate helpful constraint information to client applications.
300-
(Double-quotes are required for constraint names that contain spaces.)
301-
If not specified, the system generates a name.
300+
(Double-quotes are needed to specify constraint names that contain spaces.)
301+
If a constraint name is not specified, the system generates a name.
302302
</para>
303303
</listitem>
304304
</varlistentry>

0 commit comments

Comments
 (0)