| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add CREATE SCHEMA ... LIKE support |
| Date: | 2026-02-06 15:23:45 |
| Message-ID: | 5725e6e6-d823-4d00-ae23-eda70a422bd9@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 :)
Best, Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavlo Golub | 2026-02-06 15:27:00 | Re: [PATCH] Add last_executed timestamp to pg_stat_statements |
| Previous Message | Marcos Pegoraro | 2026-02-06 15:19:03 | Re: Add CREATE SCHEMA ... LIKE support |