|
34 | 34 | </para> |
35 | 35 |
|
36 | 36 | <para> |
37 | | - This problem can appear when querying information schema viewslike |
38 | | -<literal>referential_constraints</>, <literal>check_constraints</>, |
39 | | - <literal>domain_constraints</>, and |
40 | | - <literal>check_constraint_routine_usage</>. Some other views have |
41 | | -similarissues but contain the table name to help distinguish |
42 | | -duplicaterows, e.g. <literal>table_constraints</>, |
43 | | - <literal>constraint_table_usage</>, <literal>constraint_column_usage</>. |
| 37 | + This problem can appear when querying information schema viewssuch |
| 38 | +as <literal>check_constraint_routine_usage</>, |
| 39 | + <literal>check_constraints</>, <literal>domain_constraints</>, and |
| 40 | + <literal>referential_constraints</>. Some other views have similar |
| 41 | + issues but contain the table name to help distinguish duplicate |
| 42 | + rows, e.g., <literal>constraint_column_usage</>, |
| 43 | + <literal>constraint_table_usage</>, <literal>table_constraints</>. |
44 | 44 | </para> |
45 | 45 | </note> |
46 | 46 |
|
|