mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
404db8f9ed
The previous patch simplified CREATE SCHEMA's behavior to "execute all subcommands in the order they are written". However, that's a bit too simple, as the spec clearly requires forward references in foreign key constraint clauses to work, see feature F311-01. (Most other SQL implementations seem to read more into the spec than that, but it's not clear that there's justification for more in the text, and this is the only case that doesn't introduce unresolvable issues.) We never implemented that before, but let's do so now. To fix it, transform FOREIGN KEY clauses into ALTER TABLE ... ADD FOREIGN KEY commands and append them to the end of the CREATE SCHEMA's subcommand list. This works because the foreign key constraints are independent and don't affect any other DDL that might be in CREATE SCHEMA. For simplicity, we do this for all FOREIGN KEY clauses even if they would have worked where they were. Author: Jian He <jian.universality@gmail.com> Co-authored-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/1075425.1732993688@sss.pgh.pa.us
29 lines
677 B
SQL
29 lines
677 B
SQL
--
|
|
-- CREATE_SCHEMA
|
|
--
|
|
|
|
CREATE SCHEMA foo;
|
|
|
|
CREATE SCHEMA IF NOT EXISTS bar;
|
|
|
|
CREATE SCHEMA baz;
|
|
|
|
-- Will not be created, and will not be handled by the
|
|
-- event trigger
|
|
CREATE SCHEMA IF NOT EXISTS baz;
|
|
|
|
CREATE SCHEMA element_test
|
|
CREATE TABLE foo (id int)
|
|
CREATE VIEW bar AS SELECT * FROM foo;
|
|
|
|
CREATE SCHEMA regress_schema_1
|
|
CREATE TABLE t4(
|
|
b INT,
|
|
a INT REFERENCES t5 DEFERRABLE INITIALLY DEFERRED NOT ENFORCED
|
|
REFERENCES t6 DEFERRABLE INITIALLY DEFERRED,
|
|
CONSTRAINT fk FOREIGN KEY (a) REFERENCES t6 DEFERRABLE)
|
|
CREATE TABLE t5 (a INT, b INT, PRIMARY KEY (a))
|
|
CREATE TABLE t6 (a INT, b INT, PRIMARY KEY (a));
|
|
|
|
DROP SCHEMA regress_schema_1 CASCADE;
|