> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Nash > Sent: 10 March 2006 13:18 > To: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Edit grid crashes adding new > rows to table with autoincrement primary key. > > Dave, your suggestion worked ... creating a new database, and > a new table within it made it possible to edit the table > without error. For completeness, the new table definition > appears below, but it's pretty clear that there's no > meaningful difference between it and the one that didn't work: > > CREATE TABLE "TestTable" > ( > "keyColumn" int8 NOT NULL DEFAULT > nextval('"TestTable_keyColumn_seq"'::regclass), > "myDataColumn" varchar(30), > CONSTRAINT "TestTable_pkey" PRIMARY KEY ("keyColumn") > ) > WITHOUT OIDS; > ALTER TABLE "TestTable" OWNER TO postgres; > > Based on this result I went back to the original database, > created a new table with an identical definition, and tried > to edit the new table. It worked just fine. > > One pattern that suggests itself is that the troublesome > tables were ones for which I had changed the schema, by > deleting the primary key column and adding a new one. The > tables were empty when I did this, so I didn't think that it > would be a problem.
Interesting. Out of interest (if you still have it), what does pg_dump think the schema looks like? It sounds like pgAdmin is misreading the schema somehow, causing the crash - most likely when it tries to detect the primary key. One thought - in the edit grid, did the int8 column have [PK] in the column header? > I guess that the old idea in database engineering of doing > the work to get the schema right the first time around really > applies in this case :) . :-) Regards, Dave ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
