From: | Trurl McByte <trurl(at)realtor3d(dot)odessa(dot)ua> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dump |
Date: | 2000-06-07 21:27:50 |
Message-ID: | Pine.LNX.4.20.0006080020420.30639-100000@trurl.anything3d.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 7 Jun 2000 (Yesterday), Tom Lane wrote:
TL> Trurl McByte <trurl(at)realtor3d(dot)odessa(dot)ua> writes:
TL> > Error in dumpig defaults on serial type!
TL> > If table name have non-statndart name (example: "Order")
TL> > sequenser auto created with name "Order_id_seq".
TL> > In the dump filed definition is:
TL> > ...
TL> > "id" int4 DEFAULT nextval ( 'Order_id_seq' ) NOT NULL,
TL> > ...
TL> > , but need:
TL> > ...
TL> > "id" int4 DEFAULT nextval ( '"Order_id_seq"' ) NOT NULL,
TL> > ...
TL>
TL> Hmm. This is not pg_dump's fault: the default expression is actually
TL> being stored that way in the database. Someone seems to have thought
TL> it was a good idea to strip the double quotes at parse time instead
TL> of run time :-(.
In the same dump pg_dump writes the following:
...
CREATE SEQUENCE "Order_id_seq" start 0 increment 1 maxvalue 2147483647 minvalue 1 cache 1 ;
SELECT nextval ('"Order_id_seq"');
...
Quite probably and serial type it is possible to generate differently.
TL>
TL> Will fix for 7.1 ... in the meantime, don't name your sequences that way
TL> ...
I shall wait for...
TL>
TL> regards, tom lane
Thanx
--
Trurl McByte, Capt. of StasisCruiser "Prince"
|InterNIC: AR3200 RIPE: AR1627-RIPE|
|--98 C3 78 8E 90 E3 01 35 87 1F 3F EF FD 6D 84 B3--|
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Jennis | 2000-06-07 21:29:53 | Re: Postgresql |
Previous Message | T.J.Farrell | 2000-06-07 20:41:57 | PostgreSQL and multiple database access |