> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 18 February 2004 10:13
> To: Christopher Kings-Lynne
> Cc: mdoggett@coas.oregonstate.edu; [pgADMIN]
> Subject: Re: [pgadmin-support] inserting new records without OIDs
>
> Christopher Kings-Lynne wrote:
>
> >> Not true. Currently, you need either OID *or* a primary key.
> >> Obviously, that id column should get a pk.
> >> We'll extend the grid some time, to accept any other unique keys
> >> also. Still, defining a PK on every table is best practice.
> >> Defining a column as serial does *not* guarantee it's unique!
> >
> >
> > Remember that unique indexes can have multiple NULL values.
>
> Shhh, didn't think of that. So we won't ever accept unique
> indices for this.
Unique + not null should be OK, but only if the data was inserted with
that constraint in place.
> > Also, oids are not guaranteed unique.
>
> AFAICS this only happens on wrap around, i.e. hopefully
> never. Being strict, we shouldn't rely on oid uniqueness, but
> in practice hopefully nobody will ever notice.
<grin>
Regards, Dave.
