Обсуждение: Assorted problems in pgAdmin 1.8.0

Hello.

During the past few days I noticed the following problems:

(1) pgAdmin main window, SQL Pane
SQL-syntax for Views shows doubled double quoted commented titles,
e.g.
  -- View: ""Books_View""

  for view "Books_View" (mixed upper and lower case is intentional).
The same is _not_ the case for tables or some other object types I checked.
This may in fact not be a problem of pgAdmin, and it is just a cosmetic
glitch.

(2) Query tool, SQL entry field
Entering a '^' (e.g. as a RegEx anchor) gives '^^'.
(On the German keyboard layout, '^' is mapped to the key exactly below the
escape key, if that is of any help).

(3) Query tool, SQL entry field
The SQL field doesn't take input from the keyboard's number block. This may
be by design, but I'm so used to using the number block in certain
situations...  (first generation Apple Pro keyboard here, the crystal
polycarbonate one with the black keys).


Hope this information helps to track 'em down :-)

Thanks for all your work, and especially for supporting OS X.
Best regards

Jörg Beyer



Environment:
Machine     PowerPC G4/400 PCI (Oct. 1999)
OS          Mac OS X 10.4.10

PostgreSQL  8.2.5
            8.3.beta2
            (both compiled from source w/ gcc 4.0.1)

pgAdmin3    1.8.0 (binary from pgadmin.org)


============================================================

Jörg Beyer
PHILIPPS-University Marburg
Dept. of Psychology
Germany

Jörg Beyer wrote:
> Hello.
>
> During the past few days I noticed the following problems:
>
> (1) pgAdmin main window, SQL Pane
> SQL-syntax for Views shows doubled double quoted commented titles,
> e.g.
>   -- View: ""Books_View""
>
>   for view "Books_View" (mixed upper and lower case is intentional).
> The same is _not_ the case for tables or some other object types I checked.
> This may in fact not be a problem of pgAdmin, and it is just a cosmetic
> glitch.

Thanks, fixed in SVN.

> (2) Query tool, SQL entry field
> Entering a '^' (e.g. as a RegEx anchor) gives '^^'.
> (On the German keyboard layout, '^' is mapped to the key exactly below the
> escape key, if that is of any help).

I can't reproduce that on my MBP, but that has a UK layout where ^ is
Shift-6.

That said, when running in XP/Bootcamp, I have seen exactly the same
problem from the key directly below escape (which - assuming it makes it
through the mail server - is §). I ran into it when I wrote a keyboard
map because I wasn't happy with the bootcamp one, so I suspect this is
Mac-wierdness that needs to be fixed in wxWidgets. I've CC'd Stefan in
the hopes that he'll be able to comment.

> (3) Query tool, SQL entry field
> The SQL field doesn't take input from the keyboard's number block. This may
> be by design, but I'm so used to using the number block in certain
> situations...  (first generation Apple Pro keyboard here, the crystal
> polycarbonate one with the black keys).

Yes, this one is a known issue - from the bugs list:

[STC] The numeric keypad doesn't work with the styled text control under
wxMac.
      wxWidgets bug ref: 1776244

Thanks, Dave.

Am 12.11.2007 11:12 Uhr schrieb Dave Page (<dpage@postgresql.org>):

> Jörg Beyer wrote:
>>
>> (2) Query tool, SQL entry field
>> Entering a '^' (e.g. as a RegEx anchor) gives '^^'.
>> (On the German keyboard layout, '^' is mapped to the key exactly below the
>> escape key, if that is of any help).
>
> I can't reproduce that on my MBP, but that has a UK layout where ^ is
> Shift-6.
>
> That said, when running in XP/Bootcamp, I have seen exactly the same
> problem from the key directly below escape (which - assuming it makes it
> through the mail server - is §). I ran into it when I wrote a keyboard
> map because I wasn't happy with the bootcamp one, so I suspect this is
> Mac-wierdness that needs to be fixed in wxWidgets. I've CC'd Stefan in
> the hopes that he'll be able to comment.

Well, if not, it's not a big problem. Certainly we have to learn to live
with minor inconveniences like this ;-)


>> (3) Query tool, SQL entry field
>> The SQL field doesn't take input from the keyboard's number block. This may
>> be by design, but I'm so used to using the number block in certain
>> situations...  (first generation Apple Pro keyboard here, the crystal
>> polycarbonate one with the black keys).
>
> Yes, this one is a known issue - from the bugs list:
>
> [STC] The numeric keypad doesn't work with the styled text control under
> wxMac.
>       wxWidgets bug ref: 1776244

Sorry for the noise. I guess I have to learn to look there first.

Thanks again

Jörg