Re: Why doesn't the SERIAL data type automatically have a

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: fmiddleton(at)verizon(dot)net, pgsql-sql(at)postgresql(dot)org
Subject: Re: Why doesn't the SERIAL data type automatically have a
Date: 2005-09-27 15:33:14
Message-ID: 1127835194.29347.12.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Mon, 2005-09-26 at 20:03, Tom Lane wrote:
> Ferindo Middleton Jr <fmiddleton(at)verizon(dot)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... :)

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Daryl Richter 2005-09-27 15:35:29 Re: how to do 'deep queries'?
Previous Message Axel Rau 2005-09-27 15:11:22 Re: Updating cidr column with network operator