On 06/02/26 12:23, Jim Jones wrote: > > > On 06/02/2026 15:42, Matheus Alcantara wrote: >> On 06/02/26 11:35, Jim Jones wrote: >>> So EXCEPT instead of EXCLUDING and LIMIT TO instead of INCLUDING. Of >>> course, assuming the proposed syntax isn't already defined in the SQL >>> standard. >>> >> >> Yeah, it could be an option but IMHO adding the LIKE on CREATE SCHEMA >> sounds more similar to what we already have for CREATE TABLE ... LIKE. >> >> Although I prefer the CREATE SCHEMA LIKE syntax I'm open to discuss >> about other syntaxes. > > Just to be clear, I also like the CREATE SCHEMA <name> LIKE > <source_schema> syntax. I was just suggesting to consider changing > EXCLUDING and INCLUDING to EXCEPT and LIMIT TO, respectively. Just to > make it more consistent with IMPORT FOREIGN SCHEMA, although I find > INCLUDING and EXCLUDING way more intuitive :) >
The idea of INCLUDING and EXCLUDING is to specify objects that should be included/excluded, e.g INCLUDING ALL EXCLUDING INDEX EXCLUDING VIEW It seems to me that LIMIT TO and EXCEPT is more related to specify which objects you want to include/exclude e.g "EXCEPT users" (where users is a table) (While I'm writing this email, Hubert Depesz has shared a similar comment about this [1]) [1] https://www.postgresql.org/message-id/aYYKQDln_qjA_CdA%40depesz.com -- Matheus Alcantara EDB: https://www.enterprisedb.com
