Ahhh, after all this time using pgadmin, this was the first time I've created
tables from scratch *and* for some reason, I didn't define the pkey (duh). 
Least I know whats going on now.  Thanks.

Quoting Dave Page <dpage@vale-housing.co.uk>:

>  
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of 
> > Keith C. Perry
> > Sent: 02 September 2005 20:43
> > To: pgadmin-support@postgresql.org
> > Subject: [pgadmin-support] Problem editing table data...
> > 
> > Greetings,
> > 
> > I apologized if I've missed a discussion on this but there 
> > seems to be a problem
> > inserting and editing table data when there is no oid column 
> > present.  I'm using
> > pgadmin 1.2.2 (slackware 10.1) and pg 8.0.3.  Has anyone else 
> > reported this? If
> > not, does anyone have an idea what might be causing this?
> 
> You need either a primary key or an oid column if you want to edit data.
> Without, pgAdmin can't properly identify rows.
> 
> Regards, Dave
> 


-- 
Keith C. Perry, MS E.E.
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com
 
____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to