From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stéphane FILLON <fillons@offratel.nc>
Cc: pgsql-sql <pgsql-sql@postgreSQL.org>
Cc: pgsql-hackers <pgsql-hackers@postgreSQL.org>
Cc: pgsql-general <pgsql-general@postgreSQL.org>
Subject: Re: [HACKERS] BUG with UNIQUE clause
Date: Wed, 15 Sep 1999 09:46:35 -0400
Message-ID: <19035.937403195@sss.pgh.pa.us> (raw)
In-Reply-To: <000f01befedd$3f26fda0$a6373ad1@portable>
"=?iso-8859-1?Q?St=E9phane_FILLON?=" <fillons@offratel.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, fillons@offratel.nc, pgsql-hackers@postgreSQL.org, pgsql-general@postgreSQL.org
Subject: Re: [HACKERS] BUG with UNIQUE clause
In-Reply-To: <19035.937403195@sss.pgh.pa.us>
References: <000f01befedd$3f26fda0$a6373ad1@portable> <19035.937403195@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox