Re: [pgadmin-support] possible bug

2016-10-25 Thread Dave Page
Hi On Mon, Oct 24, 2016 at 10:52 PM, wrote: > Hello Mailing List > > Think I found a bug in the new pgAdmin 4 running windows 7 64bit, trying to > edit stored procedures/functions in python 3 (also tested on plpgsql > functions same result) > > Order of operations > > find a function that has in

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-21 Thread Ashesh Vashi
On Wed, Sep 9, 2015 at 3:31 PM, Dave Page wrote: > Thanks - the patch looks OK to my eyeballs. Ashesh said he'd take a > look as well, and (I hope) will get it committed. :-) > Patch takes care of saving the pgFrame position only. There were many other aspect of this problem were not resolved pro

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-09 Thread Dave Page
Thanks - the patch looks OK to my eyeballs. Ashesh said he'd take a look as well, and (I hope) will get it committed. :-) On Tue, Sep 8, 2015 at 8:34 AM, Sanket Mehta wrote: > Hi Dave, > > I have created and attached the patch which will set 0 in case of any > negative coordinate for any window.

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-08 Thread Sanket Mehta
Hi Dave, I have created and attached the patch which will set 0 in case of any negative coordinate for any window. Please do review it and let me know if anything is missing. Regards, Sanket Mehta Sr Software engineer Enterprisedb On Fri, Sep 4, 2015 at 1:20 PM, Sanket Mehta wrote: > Sure Dav

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-04 Thread Sanket Mehta
Sure Dave. I will look into it and revert back Regards, Sanket Mehta Sr Software engineer Enterprisedb On Fri, Sep 4, 2015 at 1:15 PM, Dave Page wrote: > On Thu, Sep 3, 2015 at 4:48 PM, greenpm wrote: > > It appears that this is a bug in the way the pgAdmin stores the window > (or > > dialog)

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-04 Thread Dave Page
On Thu, Sep 3, 2015 at 4:48 PM, greenpm wrote: > It appears that this is a bug in the way the pgAdmin stores the window (or > dialog) location to the "pgadmin3 Preferences" file when it exits. Following > is a snippet of a typical problematic window location. Notice that the Top > is a negative nu

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-09-03 Thread greenpm
It appears that this is a bug in the way the pgAdmin stores the window (or dialog) location to the "pgadmin3 Preferences" file when it exits. Following is a snippet of a typical problematic window location. Notice that the Top is a negative number. pgAdmin should never save a negative number. If th

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-04 Thread Dave Page
On Tue, Mar 3, 2015 at 5:18 PM, John Abraham wrote: > > Here's a new solution I wasn't aware of: "Windows that support resizing from > all edges can also be moved" in this case try grabbing the side, as if you > wanted to make it narrower, but then instead of dragging it sideways (to > make it nar

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-03 Thread John Abraham
On Mar 3, 2015, at 1:47 AM, Dave Page wrote: > Hi > > On Mon, Mar 2, 2015 at 9:18 PM, mark wrote: >> Hello, >> >> >> apologies if I'm not getting the UI terms right. However, I am able to >> reproduce this fairly consistently. >> >> machine: MacbookPro11,2 >> OSX: OS X 10.10.2 (14C109) >> ke

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-03 Thread Sheldon Strauch
> On Mar 3, 2015, at 8:12 AM, John Abraham wrote: > > This is indeed a problem with OS X and, for me, is a much more common problem > with pgadmin3 than with any other application. However, I personally no > longer seem to have this problem. > > I'm not a developer of pgadmin, hopefully one

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-03 Thread John Abraham
This is indeed a problem with OS X and, for me, is a much more common problem with pgadmin3 than with any other application. However, I personally no longer seem to have this problem. I'm not a developer of pgadmin, hopefully one will chime in. From my limited knowledge and fuzzy memory, here

Re: [pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-03 Thread Dave Page
Hi On Mon, Mar 2, 2015 at 9:18 PM, mark wrote: > Hello, > > > apologies if I'm not getting the UI terms right. However, I am able to > reproduce this fairly consistently. > > machine: MacbookPro11,2 > OSX: OS X 10.10.2 (14C109) > kernel: Darwin 14.1.0 > pgAdmin3: 1.20.0 > > (not complied from sou

[pgadmin-support] Possible Bug: pgAdmin3 , OSX multi monitor quirk.

2015-03-02 Thread mark
Hello, apologies if I'm not getting the UI terms right. However, I am able to reproduce this fairly consistently. machine: MacbookPro11,2 OSX: OS X 10.10.2 (14C109) kernel: Darwin 14.1.0 pgAdmin3: 1.20.0 (not complied from source, installed from dmg file linked on pgadmin.org) Steps to reprod

Re: [pgadmin-support] Possible bug report (comment on database disappered on pgAdmin 1.16.1)

2013-02-07 Thread Dave Page
Nevermind - the reason I couldn't reproduce the issue is that it's already fixed. I must have spotted it while I was working on this change: http://git.postgresql.org/gitweb/?p=pgadmin3.git;a=commit;h=7b20a39c7f018c12901e15cc23bb827517242bd1 So, the problem will be resolved in 1.16.2. On Thu, Fe

Re: [pgadmin-support] Possible bug report (comment on database disappered on pgAdmin 1.16.1)

2013-02-07 Thread Dave Page
On Thu, Feb 7, 2013 at 9:34 AM, Vjacheslav A. wrote: > Here is log. Thanks. Like another I was sent offlist, it looks fine. Can you please run "SELECT * FROM pg_shdescription", and tell me if you see the comment you added in there? Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter:

Re: [pgadmin-support] Possible bug report (comment on database disappered on pgAdmin 1.16.1)

2013-01-17 Thread Guillaume Lelarge
On Thu, 2013-01-10 at 17:00 +0700, Kanitchet Vaiassava wrote: > Possible bug report (comment on database disappeared on pgAdmin 1.16.1) > - I found that in pgAdmin 1.16.1 COMMENT ON DATABASE disappeared on SQL pane > and in the properties of Database > However, when I reopen with pgAdmin 1.16.0 or

[pgadmin-support] Possible bug report (comment on database disappered on pgAdmin 1.16.1)

2013-01-10 Thread Kanitchet Vaiassava
Possible bug report (comment on database disappeared on pgAdmin 1.16.1) - I found that in pgAdmin 1.16.1 COMMENT ON DATABASE disappeared on SQL pane and in the properties of Database However, when I reopen with pgAdmin 1.16.0 or below the comment reappeared OS Client : Microsoft Windows XP SP3 (L

Re: [pgadmin-support] Possible Bug Version 1.8.0 Beta 5 on Windows XP Service Pack 2 Postgresql 8.3 on FreeBSD6.2

2007-09-17 Thread Dave Page
Bob wrote: > Right click on a table-> go to properties-> create pk constraint and add > column click ok. A unhandled exception occurs on my machine and pgadmin > exits. This has been fixed in SVN trunk already. Thanks, Dave ---(end of broadcast)---

[pgadmin-support] Possible Bug Version 1.8.0 Beta 5 on Windows XP Service Pack 2 Postgresql 8.3 on FreeBSD6.2

2007-09-17 Thread Bob
Right click on a table-> go to properties-> create pk constraint and add column click ok. A unhandled exception occurs on my machine and pgadmin exits.

[pgadmin-support] Possible bug.

2006-05-10 Thread [EMAIL PROTECTED]
pgAdmin3 1.4.1 Gentoo Linux wxGTK 2.6.3.2 pgAdmin doesn't remember last font choice in the Help window. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Mitch S McKenzie
CTED]>, pgAdmin Support , Dave Page cc Subject Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0 First off, do stay on the list, do not mail privately for support! Mitch S McKenzie wrote: > > I tried a snapshot version of the software and it is now fixed > (1.5

Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Andreas Pflug
Dave Page wrote: Yes, 2.6.2. I can reproduce this on Xp. It happens with any edittable combobox from what I can see (column type for ex.). You can't select a new item unless you delete the text first. I looked briefly this morning, but ran out of time. Hm; IIRC I still run an older 2.6 on my ma

Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Dave Page
reas Pflug"<[EMAIL PROTECTED]> Sent: 30/11/05 22:03:26 To: "Mitch S McKenzie"<[EMAIL PROTECTED]>, "pgAdmin Support", "Dave Page" Subject: Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0 First off, do stay on the list, do not mail privately for support!

Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Andreas Pflug
First off, do stay on the list, do not mail privately for support! Mitch S McKenzie wrote: I tried a snapshot version of the software and it is now fixed (1.5_devel). Ah, uh, what? Dave, any changes I'm not aware of? This issue should be in ctlSecurityPanel.cpp or dlgProperty.cpp, but the

Re: [pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Andreas Pflug
Mitch S McKenzie wrote: Hello, My Software Versions: pgAdminIII version = 1.4.0 postgres server version = 8.0.1 How to reproduce problem: 1. Right click on "Views" for any database that contains views and select "Grant Wizard" 2. On the Selection Tab push the "Check All" button 3. Sele

[pgadmin-support] Possible Bug - pgAdminIII 1.4.0

2005-11-30 Thread Mitch S McKenzie
Hello, My Software Versions: pgAdminIII version = 1.4.0 postgres server version = 8.0.1 How to reproduce problem: 1.  Right click on "Views" for any database that contains views and select "Grant Wizard" 2.  On the Selection Tab push the "Check All" button 3.  Select the Privileges Tab and  t

Re: [pgadmin-support] Possible bug in pgAdmin III v1.2.2

2005-10-20 Thread Andreas Pflug
A.j. Langereis wrote: To whom it may concern, My pgAdmin crashed when I tried to vacuum the "template0" database. It is of course not needed to vacuum this database, but I clicked on it by accident. When I tried it again, this time on purpose, it happened again. This is caused by launching

[pgadmin-support] Possible bug in pgAdmin III v1.2.2

2005-10-20 Thread A.j. Langereis
To whom it may concern,   My pgAdmin crashed when I tried to vacuum the "template0" database. It is of course not needed to vacuum this database, but I clicked on it by accident. When I tried it again, this time on purpose, it happened again.   The PostgreSQL database that is used is v8.0.4, t

Re: [pgadmin-support] Possible Bug

2004-10-25 Thread Dave Page
Hi,   Perhaps you have logging set to 'debug'?   Regards Dave From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Elvis E. Henríquez A."Sent: 23 October 2004 19:53To: [EMAIL PROTECTED]Subject: [pgadmin-support] Possible Bug Hi. I titled

[pgadmin-support] Possible Bug

2004-10-23 Thread Elvis E. Henríquez A.
Hi. I titled my mail Possible Bug, because I'm not sure if this is a bug. I downloaded the latest version of PgAdminIII (1.2.0 Beta 3 October 18, 2004), running on Windows XP Pro SP2 (Spanish) and I have been working using the Spanish (es_ES) Language connecting to a Linux server which has th