Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBS5BAm46895 for ; Fri, 28 Dec 2001 00:11:10 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id fBS5B0r01906; Fri, 28 Dec 2001 00:11:00 -0500 (EST) From: Bruce Momjian Message-Id: <200112280511.fBS5B0r01906@candle.pha.pa.us> Subject: Re: [SQL] An easy question about creating a primary key In-Reply-To: <21560.1007434446@sss.pgh.pa.us> "from Tom Lane at Dec 3, 2001 09:54:06 pm" To: Tom Lane Date: Fri, 28 Dec 2001 00:11:00 -0500 (EST) CC: Christopher Kings-Lynne , Ligia Pimentel , Hackers X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200112/881 X-Sequence-Number: 17003 Is this resolved? --------------------------------------------------------------------------- > "Christopher Kings-Lynne" writes: > > Oh well, it was a fun coding exercise ;) Feel free to remove the ADD UNIQUE > > stuff from command.c to see if the parser will handle it. However, your > > commit message also just implies that all you fixed was ADD PRIMARY KEY??? > > It says that because I thought that was all I was changing; I hadn't > realized the side-effects on ADD UNIQUE. -- Bruce Momjian | http://candle.pha.pa.us pgman@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