Yes, however, the documentation would be a lot clearer if it said "copies all constraints except foreign keys". I've made this known.At any rate, I've attached a new version of the function that now does copy the foreign keys. Let me know if I missed anything else.--On Thu, Sep 10, 2015 at 9:09 AM, Igor Neyman <ineyman@xxxxxxxxxxxxxx> wrote:
From: Melvin Davidson [mailto:melvin6925@xxxxxxxxx]
Sent: Wednesday, September 09, 2015 4:48 PM
To: Igor Neyman <ineyman@xxxxxxxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: clone_schema function
Thanks Igor,
hmm, apparently the "INCLUDING CONSTRAINTS' option of "CREATE TABLE' has a glitch and only includes the primary key.
I also noticed that INCLUDING ALL generates an error, so I'll have to report that also.
I'll go eat some crow and work on a fix to add all constraints in the meantime.
It’s not a bug.
According to docs:
“Not-null constraints are always copied to the new table. CHECK constraints will only be copied if INCLUDING CONSTRAINTS is specified; other types of constraints will never be copied.”
So, FK constraints are not supposed to be copied.
Regards,
Igor Neyman
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
Attachment:
clone_schema.sql
Description: Binary data
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
