From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | David Virebayre <david(at)robbez(dot)com> |
Cc: | Euler Taveira <euler(at)eulerto(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Clarification regarding CREATE TABLE LIKE and FOREIGN KEYS |
Date: | 2023-12-01 14:17:04 |
Message-ID: | CAKFQuwa=2WOzWWD8OvJgMn3ntG5mt7EJcjcii9Lif87vGbYmcA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Dec 1, 2023 at 7:07 AM David Virebayre <david(at)robbez(dot)com> wrote:
> "INCLUDING ALL" leads people to believe *everything* is copied.
>
> The fact that it doesn't seem counter intuitive, at least to me.
>
> Therefore, it doesn't seem absurd to me to warn people about what is not
> copied.
>
> I wrote the original message hoping to help improve the documentation. I
> could write a draft if I'm allowed to.
> I do believe that clarifying this point improves the documentation. If
> there's a consensus that it doesn't, my apologies for the annoyance.
>
>
You are welcome to suggest improvements. But "all" means inclusive of
every individual item listed on that page. You don't get stuff in "all"
that you cannot specify individually and you cannot specify references
clauses individually.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2023-12-02 01:10:28 | libpq-ssl suggestion: |
Previous Message | Daniel Gustafsson | 2023-12-01 13:58:21 | Re: Restore to a new database from a backup (.tar) generated from |