Re: pg_dump future problem.
От | Philip Warner |
---|---|
Тема | Re: pg_dump future problem. |
Дата | |
Msg-id | 5.1.0.14.0.20030504150042.029a97a8@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | pg_dump future problem. (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
Ответы |
Re: pg_dump future problem.
|
Список | pgsql-hackers |
At 12:14 PM 4/05/2003 +0800, Christopher Kings-Lynne wrote: >CREATE TABLE really_long_name ( > a SERIAL UNIQUE >); At least in production versions, pg_dump does not do this. It will dump it as a integer default nextval('really_long_na_seq') ) not sure about CVS. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 03 5330 3172 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-hackers по дате отправления: