| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | mdoggett(at)coas(dot)oregonstate(dot)edu, "[pgADMIN]" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: inserting new records without OIDs |
| Date: | 2004-02-18 10:12:57 |
| Message-ID: | 40333AA9.4070605@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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.
> 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.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2004-02-18 11:11:01 | Re: inserting new records without OIDs |
| Previous Message | Christopher Kings-Lynne | 2004-02-18 04:46:47 | Re: inserting new records without OIDs |