|
Home > Archive > Pgadmin > September 2005 > Problem editing table data...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problem editing table data...
|
|
| Keith C. Perry 2005-09-02, 8:24 pm |
| 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?
--
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 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly
| |
| Dave Page 2005-09-02, 8:24 pm |
|
> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] 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
---------------------------(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
| |
| Andreas Pflug 2005-09-02, 8:24 pm |
| Dave Page wrote:[color=darkred
]
>
>
>
This is number one on the FAQ...
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
| |
| Keith C. Perry 2005-09-03, 8:24 pm |
| 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>:
>
>
>
> 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
|
|
|
|
|