From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: fmiddleton@verizon.net
Cc: pgsql-sql@postgresql.org
Subject: Re: Why doesn't the SERIAL data type automatically have a
Date: Tue, 27 Sep 2005 10:33:14 -0500
Message-ID: <1127835194.29347.12.camel@state.g2switchworks.com> (raw)
In-Reply-To: <5899.1127782998@sss.pgh.pa.us>
References: <4338961E.20100@verizon.net>
<5899.1127782998@sss.pgh.pa.us>
On Mon, 2005-09-26 at 20:03, Tom Lane wrote:
> Ferindo Middleton Jr <fmiddleton@verizon.net> writes:
> > Is there some reason why the SERIAL data type doesn't automatically have
> > a UNIQUE CONSTRAINT.
>
> It used to, and then we decoupled it. I don't think "I have no use for
> one without the other" translates to an argument that no one has a use
> for it ...
I have to admit, right after the change was made, I was of the opinion
that no one would ever need that. Then, a few months later, it was
exactly what I needed for some project... :)
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us, fmiddleton@verizon.net
Subject: Re: Why doesn't the SERIAL data type automatically have a
In-Reply-To: <1127835194.29347.12.camel@state.g2switchworks.com>
* 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