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:[EMAIL PROTECTED] >Sent: Tuesday, February 17, 2004 9:15 AM >To: [EMAIL PROTECTED] >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 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
