| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stéphane FILLON <fillons(at)offratel(dot)nc> |
| Cc: | "pgsql-sql" <pgsql-sql(at)postgreSQL(dot)org>, "pgsql-hackers" <pgsql-hackers(at)postgreSQL(dot)org>, "pgsql-general" <pgsql-general(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] BUG with UNIQUE clause |
| Date: | 1999-09-15 13:46:35 |
| Message-ID: | 19035.937403195@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
"=?iso-8859-1?Q?St=E9phane_FILLON?=" <fillons(at)offratel(dot)nc> writes:
> The UNIQUE constraint doesn't work on a field if I use a DEFAULT clause
> on a table.
This sounds closely related to a fix that Thomas Lockhart just made.
IIRC the complained-of symptom was that PRIMARY KEY on one column plus
UNIQUE on another didn't work, but the real problem was that PRIMARY
KEY implies UNIQUE and the table declaration code was getting confused
by two different UNIQUE columns in one table. It could be that his fix
addresses your problem too. Check the pghackers archives for the
last couple weeks to find the patch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-09-15 14:00:02 | Re: [HACKERS] Permission problem with COPY FROM |
| Previous Message | Gregoire Pichon | 1999-09-15 09:54:00 | crypted field |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-09-15 14:00:02 | Re: [HACKERS] Permission problem with COPY FROM |
| Previous Message | Vadim Mikheev | 1999-09-15 05:46:15 | 6.6 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-09-15 13:53:02 | Re: [SQL] to do's? |
| Previous Message | Molnár László | 1999-09-15 10:55:27 | trees in postgres |