Thread: pgAdmin III 1.2.2 edit grid crashes with single-column tables
Hello all,
I have got a strange problem with pgAdmin III 1.2.2 on Windows XP SP2.
I've got a table with only one column (also primary key) of type
varchar. pgAdmin crashes every time I insert a new row in the edit grid,
either when hitting enter or pressing the store button. The crash
actually happens after committing the change. The new data is there when
I restart pgAdmin.
Can anybody reproduce this?
Regards,
Harald Fricke
Last entries from pgadmin.log:
2005-10-21 15:37:24 INFO : Creating EditGrid
2005-10-21 15:37:24 INFO : Running query SELECT * FROM osnames ORDER
BY name ASC
2005-10-21 15:37:24 QUERY : Thread Query SELECT * FROM osnames ORDER BY
name ASC
2005-10-21 15:37:24 INFO : Creating pgSet object
2005-10-21 15:37:24 QUERY : Set query (192.168.10.147:5432): SELECT
n.nspname AS nspname, relname, t.typname, nt.nspname AS typnspname,
attname, COALESCE(b.oid, t.oid) AS basetype, atthasdef, adsrc, CASE WHEN t.typbasetype::oid=0 THEN att.atttypmod
else
t.typtypmod END AS typmod, CASE WHEN t.typbasetype::oid=0 THEN att.attlen else t.typlen END
AS typlen FROM pg_attribute att JOIN pg_type t ON t.oid=att.atttypid JOIN pg_namespace nt ON nt.oid=t.typnamespace
JOINpg_class c ON c.oid=attrelid JOIN pg_namespace n ON n.oid=relnamespace LEFT OUTER JOIN pg_type b ON
b.oid=t.typbasetype LEFT OUTER JOIN pg_attrdef def ON adrelid=attrelid AND adnum=attnum WHERE attnum > 0 AND NOT
attisdroppedAND attrelid=45897::oid ORDER BY attnum
2005-10-21 15:37:24 INFO : Creating pgSet object
2005-10-21 15:37:24 INFO : Destroying pgSet object
2005-10-21 15:37:27 INFO : Destroying pgSet object
2005-10-21 15:37:32 QUERY : Set query (192.168.10.147:5432): INSERT
INTO osnames(name) VALUES ('gaga'::pg_catalog."varchar")
2005-10-21 15:37:32 INFO : Creating pgSet object
2005-10-21 15:37:32 INFO : Destroying pgSet object
~
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of > Dr. Harald Fricke > Sent: 21 October 2005 14:44 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] pgAdmin III 1.2.2 edit grid > crashes with single-column tables > > Hello all, > I have got a strange problem with pgAdmin III 1.2.2 on > Windows XP SP2. > I've got a table with only one column (also primary key) of type > varchar. pgAdmin crashes every time I insert a new row in the > edit grid, > either when hitting enter or pressing the store button. The crash > actually happens after committing the change. The new data is > there when > I restart pgAdmin. > > Can anybody reproduce this? Not on 1.4 beta 3. Can you give that a try please? Thanks, Dave.
Dave Page wrote: > >>-----Original Message----- (...) >>Hello all, >>I have got a strange problem with pgAdmin III 1.2.2 on >>Windows XP SP2. >>I've got a table with only one column (also primary key) of type >>varchar. pgAdmin crashes every time I insert a new row in the >>edit grid, >>either when hitting enter or pressing the store button. The crash >>actually happens after committing the change. The new data is >>there when >>I restart pgAdmin. >> >>Can anybody reproduce this? > > > Not on 1.4 beta 3. Can you give that a try please? (...) On my computer, 1.4 beta 3 crashes too. I also get a warning in slightly broken German that my server is running on Windows and cannot handle UTF8 correctly. The server is 8.0.1 running on Novell SLES 9. Regards, Harald Fricke
Dr. Harald Fricke wrote: > Dave Page wrote: > >> >>> -----Original Message----- > > (...) > >>> Hello all, >>> I have got a strange problem with pgAdmin III 1.2.2 on Windows XP >>> SP2. I've got a table with only one column (also primary key) of type >>> varchar. pgAdmin crashes every time I insert a new row in the edit >>> grid, either when hitting enter or pressing the store button. The >>> crash actually happens after committing the change. The new data is >>> there when I restart pgAdmin. >>> >>> Can anybody reproduce this? >> >> >> >> Not on 1.4 beta 3. Can you give that a try please? > > (...) > > On my computer, 1.4 beta 3 crashes too. Can't reproduce this with CREATE TABLE t(v varchar primary key) > I also get a warning in slightly broken German :-) If you like to provide a better text... See docs/de_DE/hints > that my server is running on Windows and cannot handle > UTF8 correctly. The server is 8.0.1 running on Novell SLES 9. Fixed in post-Beta3. Regards, Andreas