Skip site navigation (1) Skip section navigation (2)

Re: inserting new records without OIDs

From: "Matt Doggett" <mdoggett(at)coas(dot)oregonstate(dot)edu>
To: "'Andreas Pflug'" <pgadmin(at)pse-consulting(dot)de>
Cc: "'[pgADMIN]'" <pgadmin-support(at)postgresql(dot)org>
Subject: Re: inserting new records without OIDs
Date: 2004-02-17 19:02:08
Message-ID: 000801c3f588$8ab263d0$2441c180@oce.orst.edu (view raw or flat)
Thread:
Lists: pgadmin-support
Ahhhh. You are correct. Turns out I was failing to define my serial 'id'
attribute as a primary key. My bad. Thanks for the help.

MD

>-----Original Message-----
>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>Sent: Tuesday, February 17, 2004 9:15 AM
>To: mdoggett(at)coas(dot)oregonstate(dot)edu
>Cc: [pgADMIN]
>Subject: Re: [pgadmin-support] inserting new records without OIDs
>
>Matt Doggett wrote:
>
>>Ooops. I sent this yesterday to the wrong maillist address. Sorry.
I'll
>>repost here.
>>
>>MD
>>-----Original Message-----
>>When I create a new table that does not have OIDs (the Has OIDs
checkbox
>>is off and I'm using a serial column type to id my records), then I
>>CANNOT insert new data records using the Edit Data window.  There is
no
>>blank row (with an asterisk *) in which to enter new data.  In other
>>words, I've discovered that you MUST use OIDs to be able to insert new
>>records with the Edit window.
>>
>>
>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!
>
>Regards,
>Andreas



In response to

pgadmin-support by date

Next:From: Dave PageDate: 2004-02-17 19:59:50
Subject: Re: connection dropping continued
Previous:From: Andreas PflugDate: 2004-02-17 17:41:36
Subject: Re: connection dropping continued

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group