Thread: Bug in 'query tool'

Dear List,

I found an other bug related to special characters.
Try insert the following query:
select translate(s2, 'ÁÉÍÓÖŐÜŰÚ', 'áéíóöőüűú');
save the query into file. You will get a 0 byte length file.

Regards,   Ferenc

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of YourSoft
> Sent: 22 May 2006 15:15
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Bug in 'query tool'
>
> Dear List,
>
> I found an other bug related to special characters.
> Try insert the following query:
> select translate(s2, 'ÁÉÍÓÖŐÜŰÚ', 'áéíóöőüűú'); save the
> query into file. You will get a 0 byte length file.

What version of PostgreSQL? I get the following for that query in 8.1.4:

ERROR:  character 0xc590 of encoding "UTF8" has no equivalent in "LATIN1"

Though 8.1.4 does include *serious* hardening of the encoding validation routines.

Regards, Dave.

> -----Original Message-----
> From: YourSoft [mailto:yoursoft@freemail.hu]
> Sent: 23 May 2006 08:08
> To: Dave Page
> Subject: Re: [pgadmin-support] Bug in 'query tool'
>
> Dear Dave,
>
> My PostgreSQL version is: 8.1.3 (under WinXp Hungarian  -
> latest win32 release).
> My pgAdmin version is: 1.4.2 (win32 - latest release).
>
> I think my code page is LATIN2.
>
> If you need any help in this (log files, try a debugged
> pgAdmin version on my computer etc.), I will help to you. :-)

Can you try it under PostgreSQL 8.1.4 please (it is released - I built
it myself yesterday). As I mentioned it has vastly improved encoding
validators to detect and reject invalid byte sequences. The error I was
seeing yesterday implies that something in your test was not valid in
UTF8 which might also be why pgAdmin fails to save it properly.

Regards, Dave.