From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, <pgsql-hackers(at)postgresql(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Subject: | Re: pg_dump: use ALTER TABLE for PKs |
Date: | 2002-02-19 21:37:46 |
Message-ID: | 3.0.5.32.20020220083746.01e2e990@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 13:07 19/02/02 -0800, Stephan Szabo wrote:
>>
>> CREATE TABLE PARENT(F1 INT PRIMARY KEY);
>> CREATE TABLE CHILD(...) INHERIT PARENT
>>
>> this should create a PK on CHILD; what does pg-dump and the ALTER TABLE
>> implementation do? Not sure how it should work, but ultimately we need to
>
>Unless it was changed between rc2 and release, the above type of
>sequence does not end up with a primary key on child(f1).
Interesting, - that makes pg_dumps job easier. Are any constraints ever
inherited?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-02-19 22:05:56 | Re: pg_dump: use ALTER TABLE for PKs |
Previous Message | Jean-Michel POURE | 2002-02-19 21:33:43 | Re: [HACKERS] UTF-8 data migration problem in Postgresql 7.2 |