From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Ligia Pimentel" <lmpimentel(at)yahoo(dot)com>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [SQL] An easy question about creating a primary key |
Date: | 2001-12-04 02:23:19 |
Message-ID: | GNELIHDDFBOCMGBFGEFOCEKHCAAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-odbc pgsql-sql |
> I think you've forgotten your own work, Chris.
>
> regression=# create table foo (bar int not null);
> CREATE
> regression=# alter table foo add primary key (bar);
> NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
> 'foo_pkey' for table 'foo'
> CREATE
> regression=#
Bizarre. That patch was never committed. If you check
src/backend/commands/command.c and search for 'CONSTR_' you'll notice that
the CONSTR_UNIQUE function I implemented is there, but CONSTR_PRIMARY is
definitely not being handled. (I'm looking at the 7.2b2 source code)
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-12-04 02:29:49 | Re: [SQL] An easy question about creating a primary key |
Previous Message | Manuel Cabido | 2001-12-04 02:18:45 | Re: date formatting and tab-complete patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-12-04 02:29:49 | Re: [SQL] An easy question about creating a primary key |
Previous Message | Tom Lane | 2001-12-04 02:12:21 | Re: An easy question about creating a primary key |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-12-04 02:29:49 | Re: [SQL] An easy question about creating a primary key |
Previous Message | Tom Lane | 2001-12-04 02:12:21 | Re: An easy question about creating a primary key |