Commite07ae21

committed

Document that an SQL-standard-compliant query that expects a unique row

from information_schema.referential_constraints might return several inPostgres because we allow duplicate-named constraints in the sameschema.

1 parentb05186f commite07ae21Copy full SHA for e07ae21

File tree

+13

-0

lines changed

+13

-0

lines changed

Lines changed: 13 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -3211,6 +3211,19 @@ ORDER BY c.ordinal_position;`
`3211`	`3211`	`</tbody>`
`3212`	`3212`	`</tgroup>`
`3213`	`3213`	`</table>`
	`3214`	`+`
	`3215`	`+ <note>`
	`3216`	`+ <para>`
	`3217`	`+ The SQL standard requires constraint names to be unique within a`
	`3218`	`+ schema; <productname>PostgreSQL</productname>, however, does not`
	`3219`	`+ enforce this restriction. If duplicate-named constraints are`
	`3220`	`+ stored in the same <productname>PostgreSQL</productname> schema, a`
	`3221`	`+ standard-compliant query that expects to return one row might`
	`3222`	`+ return several, one for each matching constraint stored in the`
	`3223`	`+ specified schema.`
	`3224`	`+ </para>`
	`3225`	`+ </note>`
	`3226`	`+`
`3214`	`3227`	`</sect1>`
`3215`	`3228`
`3216`	`3229`	`<sect1 id="infoschema-role-column-grants">`

Comments

(0)