"Ferindo Middleton Jr" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Is there some reason why the SERIAL data type doesn't automatically have a
> UNIQUE CONSTRAINT. It seems that the main reason for using it is so that
> the value for this field keeps changing automatically and
You're right, Tom. I'm sure someone has a use for a serial field that
isn't unique. I just assumed that it was. I guess I didn't read the
documentation closely enough. At any rate, I had a table using a serial
field that I had to restore to a previous date when I noticed that I
forgot to set th
Ferindo Middleton Jr <[EMAIL PROTECTED]> 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
