[pgadmin-support] pgAdmin: not remembering passwords

2006-06-29 Thread postgresql . org
In reference to this thread, from several months ago: http://archives.postgresql.org/pgadmin-support/2005-12/msg00021.php I don't know if this was ever solved elsewhere on the list, but it took me some time to figure out what I think is the cause of the symptom. I believe whenever I specify

[pgadmin-support] pgAdmin 1.4.3 bug with delete button in win32

2006-08-02 Thread postgresql . org
I noticed one of the new features on the win32 side for pgAdmin is that when you're viewing a row and press "delete" you get a prompt to delete the row. That's a pretty cool feature, except it also triggers that prompt if you're editing a field within a row, and might be wanting to delete some

Re: [pgadmin-support] pgAdmin 1.4.3 bug with delete button in win32

2006-08-02 Thread postgresql . org
Dave Page wrote: That's a pretty cool feature, except it also triggers that prompt if you're editing a field within a row, and might be wanting to delete some characters within the field, not the whole row. I can't reproduce that here - it deletes the character to the right of the cursor. T

Re: [pgadmin-support] pgAdmin 1.4.3 bug with delete button in win32

2006-08-02 Thread postgresql . org
Melvin Davidson wrote: You just need to use position the cursor after the character and press 'Backspace' to delete it. Yes, thanks for the workaround but I'd already figured that out. You should not be using the "Delete" key to delete characters. Surely you're joking. jl

Re: [pgadmin-support] pgAdmin 1.4.3 bug with delete button in win32

2006-08-02 Thread postgresql . org
Melvin Davidson wrote: I cannot duplicate your problem either. Is it possible you are using/have a keyboard mapping utility program which has redefined the function of the delete key? I don't think so, but if no one else can reproduce this it must be something strange about my workstation.

Re: SPAM: MEDIUM * Re: [pgadmin-support] pgAdmin 1.4.3 bug with

2006-08-02 Thread postgresql . org
Dave Page wrote: I'm running on WinXP SP2 with nothing else too funky going on. Can you think of anything in my configuration that might be causing this? Nope. There have been changes in that code as you know - can you figure out an exact procedure to recreate the problem? Perhaps it takes som