|
32 | 32 | automatically-generated constraint names avoid duplicates in the |
33 | 33 | same schema, but users can specify such duplicate names. |
34 | 34 | </para> |
| 35 | + |
| 36 | + <para> |
| 37 | + This problem can appear when querying information schema views like |
| 38 | + <literal>referential_constraints</>, <literal>check_constraints</>, |
| 39 | + <literal>domain_constraints</>, and |
| 40 | + <literal>check_constraint_routine_usage</>. Some other views have |
| 41 | + similar issues but contain the table name to help distinguish |
| 42 | + duplicate rows, e.g. <literal>table_constraints</>, |
| 43 | + <literal>constraint_table_usage</>, <literal>constraint_column_usage</>. |
| 44 | + </para> |
35 | 45 | </note> |
36 | 46 |
|
37 | 47 |
|
|