Re: CREATE SCHEMA ... CREATE DOMAIN support
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>,
jian he <jian.universality@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-12-01T05:53:04Z
Lists: pgsql-hackers
Kirill Reshke <reshkekirill@gmail.com> writes: > 3) Why do we delete this in `create_schema.sgml`? Is this untrue? It > is about order of definition, not creation, isn't it? >> - The SQL standard specifies that the subcommands in <command>CREATE >> - SCHEMA</command> can appear in any order. In context with the following sentence, what that is really trying to say is that the spec requires us to re-order the subcommands to eliminate forward references. After studying the text I cannot find any such statement. Maybe I missed something --- there's a lot of text --- but it's sure not to be detected in any obvious place like 11.1 <schema definition>. (I'd be curious to know how other major implementations handle this. Are we the only implementation that ever read the spec that way?) regards, tom lane
Commits
-
Don't try to re-order the subcommands of CREATE SCHEMA.
- a9c350d9ee66 19 (unreleased) landed
-
Execute foreign key constraints in CREATE SCHEMA at the end.
- 404db8f9edbb 19 (unreleased) landed
-
Support more object types within CREATE SCHEMA.
- d516974840f4 19 (unreleased) landed