|
23 | 23 |
|
24 | 24 | <note>
|
25 | 25 | <para>
|
26 |
| - The SQL standard requires constraint names to be unique within a |
27 |
| - schema; <productname>PostgreSQL</productname>, however, does not |
28 |
| - enforce this restriction. If duplicate-named constraints are |
29 |
| - stored in the same <productname>PostgreSQL</productname> schema, |
30 |
| - a standard-compliant query that expects to return one matching |
31 |
| - constraint row might return several, one row for each matching |
32 |
| - constraint stored in the specified schema. |
| 26 | + When querying the database for constraint information, it is possible |
| 27 | + for a standard-compliant query that expects to return one row to |
| 28 | + return several. This is because the SQL standard requires constraint |
| 29 | + names to be unique within a schema, but |
| 30 | + <productname>PostgreSQL</productname> does not enforce this |
| 31 | + restriction. <productname>PostgreSQL</productname> |
| 32 | + automatically-generated constraint names avoid duplicates in the |
| 33 | + same schema, but users can specify such duplicate names. |
33 | 34 | </para>
|
34 | 35 | </note>
|
35 | 36 |
|
|