Re: Suggested fix for pg_dump

At 00:03 13/01/01 +1100, Philip Warner wrote:
>At 13:29 7/01/01 -0500, Tom Lane wrote:
>>The Hermit Hacker <scrappy@hub.org> writes:
>>> Essentially, worst case scenario, we are going from 'broken->broken' ...
>>
>>No, I don't think so.  The current pg_dump code is only broken if
>>you've renamed a column involved in a foreign-key dependency (if I
>>understood the thread correctly).  But Philip is proposing to change
>>pg_dump to rely on alter table add constraint for *all* PRIMARY KEY
>>constructs.  
>
>I've got a version of this working now, but it raises a further question:

Apart from the fact that 
   ALTER TABLE ADD CONSTRAINT name PRIMARY KEY(fields);

is not supported in 7.1. Oh well.




----------------------------------------------------------------
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   |/