From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [PATCHES] pg_dump primary keys |
Date: | 1999-12-11 12:47:31 |
Message-ID: | Pine.GSO.4.02A.9912111343150.5375-100000@Krabba.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 11 Dec 1999, Oleg Bartunov wrote:
> I have a problem with pg_dump (6.5.3) if I use
> create table foo (
> a text default foo_function()
> );
> where foo_function() is my function.
> pg_dump dumps create table first and create function
> later. Obvioulsy restoring doesn't works and
> I have to edit dump file. It's rather annoying.
> Is it fixed in current tree ?
What though if a function accesses a table? Which one goes first? Do we
have to maintain a network of dependencies in pg_dump? Eventually we'll
probably have to, with all the foreign key stuff coming up. Gloomy
prospects.
-Peter
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-12-11 12:48:19 | Re: [HACKERS] LONG |
Previous Message | Hannu Krosing | 1999-12-11 09:28:02 | Re: [HACKERS] 6.6 release |