Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB42sAm41784 for ; Mon, 3 Dec 2001 21:54:10 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fB42s6i21563; Mon, 3 Dec 2001 21:54:06 -0500 (EST) To: "Christopher Kings-Lynne" cc: "Ligia Pimentel" , "Hackers" Subject: Re: [SQL] An easy question about creating a primary key In-reply-to: References: Comments: In-reply-to "Christopher Kings-Lynne" message dated "Tue, 04 Dec 2001 10:50:06 +0800" Date: Mon, 03 Dec 2001 21:54:06 -0500 Message-ID: <21560.1007434446@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/73 X-Sequence-Number: 16221 "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. regards, tom lane