Hi Kurt,

sorry for the (so long) delay. I'm forwarding this upstream as I have no
way here to rapidly reproduce this.

@pgadmin-hackers: kurt is facing the issue described below. Can someone
reproduce? Anyone aware of it?

Regards,
Raphaël

Kurt Roeckx wrote:
> Package: pgadmin3
> Version: 1.4.3-1
>
> Hi,
>
> I have 2 SQL windows opens. Te first one is busy retrieving rows
> from the database (which takes about 60 seconds). If I then type
> something in the second sql view, about half of my key presses are
> getting lost. This is rather annoying.
>
> Note that it only happens when the first window is also doing something,
> if that stopped, I don't have the problem anymore.
>


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailtogadmin-hackers-owner@postgresql.org] On Behalf Of
> Raphaël Enrici
> Sent: 27 September 2006 20:16
> To: PgAdmin Hackers
> Cc: Kurt Roeckx; 383901-forwarded@bugs.debian.org
> Subject: Re: [pgadmin-hackers] Bug#383901: pgadmin3: Lost key
> presses when other view is active.
>
> Hi Kurt,
>
> sorry for the (so long) delay. I'm forwarding this upstream
> as I have no
> way here to rapidly reproduce this.
>
> @pgadmin-hackers: kurt is facing the issue described below.
> Can someone
> reproduce? Anyone aware of it?
>
> Regards,
> Raphaël
>
> Kurt Roeckx wrote:
> > Package: pgadmin3
> > Version: 1.4.3-1
> >
> > Hi,
> >
> > I have 2 SQL windows opens. Te first one is busy retrieving rows
> > from the database (which takes about 60 seconds). If I then type
> > something in the second sql view, about half of my key presses are
> > getting lost. This is rather annoying.
> >
> > Note that it only happens when the first window is also
> doing something,
> > if that stopped, I don't have the problem anymore.

Hi Raph,

Much of the code in the query tool has been rewritten for 1.6. Can this problem be reproduced in SVN/beta 1?

I've tried in Slackware here, and I could reproduce the problem even when I wasn't running another query, however I could also reproduce it in Kword and Kate so I'm putting that down to the fact that I'm running in a VMWare virtual machine - obviously the last two cases aren't pgAdmin bugs :-)

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Hi Dave,

Dave Page wrote:
>
> Hi Raph,
>
> Much of the code in the query tool has been rewritten for 1.6. Can this problem be reproduced in SVN/beta 1?

I've not packaged it at all ATM. I've contacted back Ron last night to
ask him for an experimental wxWidgets 2.7 package. However, there is
absolutely no chance to get this included into the next debian/stable
release which is planned for the beginning of December.

Just a few word on this so that you are aware of what's going on at d.o.:
pgAdmin III 1.4.3 is in debian/testing ATM and unless something critical
happens until the debian/stable release date that's the one which will
be included with this debian release named Etch (the first version of
pgAdmin III included into debian/stable!). So, I may need help in the
future with bugs concerning 1.4.3 and won't be able to go to 1.6 or 1.8
or 2.0 to solve them... Hope you'll be able to help and I won't be alone
on my side

However, as soon as I have something up'n running for 1.6 I'll give it a
try to check if it's fixed.


> I've tried in Slackware here, and I could reproduce the problem even when I wasn't running another query, however I could also reproduce it in Kword and Kate so I'm putting that down to the fact that I'm running in a VMWare virtual machine - obviously the last two cases aren't pgAdmin bugs :-)



Thanks,
Raph


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match