Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA73041; Mon, 26 Jul 1999 09:37:58 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id JAA02203; Mon, 26 Jul 1999 09:37:49 -0400 (EDT) From: Bruce Momjian Message-Id: <199907261337.JAA02203@candle.pha.pa.us> Subject: Re: [SQL] database design SQL prob. In-Reply-To: from "D'Arcy J.M. Cain" at "Jul 26, 1999 06:30:57 am" To: pgsql-hackers@postgreSQL.org Date: Mon, 26 Jul 1999 09:37:49 -0400 (EDT) CC: Don Yury , pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Thus spake Don Yury > > > Not completely accurate. Create some tables using both methods then > > However, if you create table with primary key, for example > > > > create table tab( > > id int4 primary key, > > ... > > ); > > > > and make dump of database, it will write in dump file > > > > create table tab( > > id int4, > > ... > > ); > > create unique index "tab_pkey" on "tab" using btree ("id"); > > So it does. I thought that this was fixed in 6.5 but it seems not. Is > this on the TODO list? No. Please give me a line to add. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026