Crash condition

From: "Virgil Frum" <virgil(at)livius(dot)net>
To: <pgadmin-support(at)postgresql(dot)org>
Subject: Crash condition
Date: 2004-10-20 17:52:26
Message-ID: 004301c4b6cd$8ff8ba90$310210ac@virgil
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

pgAdmin3 ver. 1.2.0 Post-Beta (oct 16 2004)

Steps to follow in edit grid:
1. Change value of an arbitrary column on last row then click on the same
row but different column so row is not updated ('Save[d] changed row.'
button is enabled).
2. Select previous row (n-1) and last row.
3. Press Delete button
4. Click 'Saved changed row.' button and pgadmin3 will crash.

If at step 2 will select only last row, pgadmin3 won't crash but last empty
line (labeled *) will contain 'changed' row after step 4, row deleted at
step 3. Generalizing, crashing can be reproduced if selection is made from
x-1 to n where x is number of 'changed' row and n number of last row.
I've attached Dr. Watson's log. I don't know if it's very helpful 'case I
don't have a .dbg file for pgadmin3.

Virgil

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.776 / Virus Database: 523 - Release Date: 12.10.2004

Attachment Content-Type Size
drwtsn.txt text/plain 5.8 KB

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Andreas Pflug 2004-10-20 18:11:06 pgAdmin III 1.2 Beta-3 released
Previous Message Sim Zacks 2004-10-20 14:18:08 Re: Bug: PGAdmin + plpythonu + windows