Thread: Another release note?

Is it worth mentioning this as a compatibility issue?

"Prior to PostgreSQL 7.3, serial  implied UNIQUE. This is no longer 
automatic. If you wish a serial column to be in a unique constraint or a 
primary key, it must now be specified, same as with any other data type."

Chris

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> Is it worth mentioning this as a compatibility issue?
> "Prior to PostgreSQL 7.3, serial  implied UNIQUE. This is no longer 
> automatic. If you wish a serial column to be in a unique constraint or a 
> primary key, it must now be specified, same as with any other data type."

Er, that *was* a compatibility issue.  For 7.3.
        regards, tom lane

>>Is it worth mentioning this as a compatibility issue?
>>"Prior to PostgreSQL 7.3, serial  implied UNIQUE. This is no longer 
>>automatic. If you wish a serial column to be in a unique constraint or a 
>>primary key, it must now be specified, same as with any other data type."
> 
> 
> Er, that *was* a compatibility issue.  For 7.3.

Doh - I'm an idiot.

Christopher Kings-Lynne wrote:
> >>Is it worth mentioning this as a compatibility issue?
> >>"Prior to PostgreSQL 7.3, serial  implied UNIQUE. This is no longer 
> >>automatic. If you wish a serial column to be in a unique constraint or a 
> >>primary key, it must now be specified, same as with any other data type."
> > 
> > 
> > Er, that *was* a compatibility issue.  For 7.3.

And we did mention it in the 7.3 release notes:
    * serial columns are no longer automatically UNIQUE; thus, an index      will not automatically be created.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073