From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <s(dot)vanroye(at)easytowork(dot)nl>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Possible Bug in "View data for selected |
Date: | 2006-09-01 12:59:03 |
Message-ID: | C11DED27.12FB4%dpage@vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On 1/9/06 12:23, "Stijn Vanroye" <s(dot)vanroye(at)easytowork(dot)nl> wrote:
> Hello,
>
> I am experiencing the following (reproducable) error in pgAdmin. I'm
> posting this as information. If this bug is already known, my apologies.
>
> I'm running pgAdmin version 1.4.3 (which is the latest stable I
> presume), Language English, downloaded the win32 zip file.
> OS: Win XP Pro SP2 Dutch with all latest updates
> Postgres backend Version: 8.1.4 for Win32
>
> Unfortunatly I do not have the luxury to download and test with the
> latest beta or development snapshot.
>
> This is the error description:
>
> I do the following:
> - open the "View data for selected object" screen for a table with an
> autoinc field as PK (fieldtype serial in combination whit a sequence)
> - edit some data (not the PK field)
> - perform an action that would confirm the changes (selecting different
> record, pressing enter key,...)
>
> pgAdmin closes entirely without an error message, other than the windows
> "report this behaviour" screen, which is shown 3 times.
That's definitely not normal - I know lot's of people use it exactly thaat
way on a regular basis, myself included. So, the question is; what's odd
about your setup?
Some thoughts:
- Does this happen on every table or just one?
- What encoding are you using?
- What does the table definition look like?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-09-01 13:09:04 | Re: Build fails on OSX using wx 2.7.0 |
Previous Message | Stijn Vanroye | 2006-09-01 11:23:52 | Possible Bug in "View data for selected object" screen |