Hi Christophe,

It does not change a thing !

If I type:
SET client_encoding TO 'LATIN9';
sdfghsdfh;

In 1.6.2, I get:
ERREUR:
État SQL :42601
Caractère : 37

When in 1.4.3, I get :
ERREUR: erreur de syntaxe sur ou près de «sdfghsdfh» au caractère 1

And in 1.6.2, but LATIN1 character set database, I get:
ERREUR: erreur de syntaxe sur ou près de «sdfghsdfh»
État SQL :42601
Caractère : 37

Let me know, if I can help some more.



Cheers,
L@u
The Computing Froggy

----- Message d'origine ----
De : Christophe Chauvet <christophe.chauvet@aznetwork.fr>
À : Laurent ROCHE <laurent_roche@yahoo.com>
Cc : pgadmin-support@postgresql.org
Envoyé le : Lundi, 15 Janvier 2007, 18h13mn 47s
Objet : Re: [pgadmin-support] Re : Still no text for error messages only numbers for 1.6.2 (aka the Saga continues)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Laurent

Can you try this

SET client_encoding TO 'LATIN9'

before sending your query ?

Christophe.

P.S .You can send me your answer in french if you prefer ?

Laurent ROCHE a écrit :
> Hi,
>
> Can anyone help me, on this one ?
>
>
> Have fun,
> L@u
> The Computing Froggy
>
> ----- Message d'origine ----
> De : Laurent ROCHE <laurent_roche@yahoo.com>
> À : pgadmin-support@postgresql.org
> Cc : guillaume@lelarge.info
> Envoyé le : Mardi, 9 Janvier 2007, 15h39mn 57s
> Objet : Still no text for error messages only numbers for 1.6.2 (aka the Saga continues)
>
> Hi All (and Guillaume),
>
>
> So I have upgraded to the latest and shiny PGAdmin 1.6.2 ... and I still have the same problem I had in 1.6.1.
>
> If I have a database set with UTF-8 character set then when I type the following (in the query tool window):
> sdfhsdfj
> I get:
> ERREUR:
> État SQL :42601
> Caractère : 1
>
> In a query tool with a database set with LATIN1 or SQL_ASCII characterset, I get:
> ERREUR: erreur de syntaxe sur ou près de «sdfhsdfj»
> État SQL :42601
> Caractère : 1
>
> Which is what I would expect (at least till the PG syntax does not change ;-) ! ).
>
> I do not have this problem with PG Admin 1.4.3, which will write:
> ERREUR: erreur de syntaxe sur ou près de «sdfhsdfj» au caractère 1
>
> Of course, you would have guessed from the error messages that I am in French locale for the client (Windows XP SP2) and for the Server (Ubuntu 6.06, PG 8.1).
>
> Let me know if you need more info about this.
>
>
>
> Cheers,
> L@u
> The Computing Froggy
>
> ----- Message d'origine ----
> De : Laurent ROCHE <laurent_roche@yahoo.com>
> À : pgadmin-support@postgresql.org
> Cc : guillaume@lelarge.info
> Envoyé le : Jeudi, 14 Décembre 2006, 16h33mn 25s
> Objet : Re : Re : Re : [pgadmin-support] No text for error messages only numbers
>
> Hi,
>
> OK, I have found what the problem is !
> My databases are in UTF8, with another charset (LATIN1, ...) that works fine.
>
> And I have checked: pgAdmin III v 1.4.3 can display the error messages of a UTF8 database (as well as non UTF8).
> So something got broken along the way !
>
> Good luck fixing it.
>
> Any estimates for the roll-out of 1.6.2 ?
> (I have read the the particulary annoying bug of empty tables not being editable is fixed in 1.6.2)
>
>
> Cheers,
> L@u
> The Computing Froggy
>
>
> ----- Message d'origine ----
> De : Guillaume Lelarge <guillaume@lelarge.info>
> À : Laurent ROCHE <laurent_roche@yahoo.com>
> Envoyé le : Vendredi, 8 Décembre 2006, 17h02mn 56s
> Objet : Re: Re : Re : [pgadmin-support] No text for error messages only numbers
>
> Laurent ROCHE a ecrit le 08/12/2006 17:01:
>> Postgres is:
>> "PostgreSQL 8.1.4 on i486-pc-linux-gnu, compiled by GCC gcc-4.0.gcc-opt (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)"
>>
>> And PgAdmin v 1.6.1 does not work when PgAdmin 1.4.3 does work.
>>
>> But, as I said in another message, strangely, on the same server, I do get error messages (with 1.6.1) with one database and no error message with the other ! ? !
>> I am going to investigate a bit more to find out what are the differences between the databases (and narrow it down to simple example) , and I will post an update.
>>
>
> OK, thanks. Just keep me informed.
>
>

- --
Christophe Chauvet <christophe.chauvet@aznetwork.fr>
AZNetwork
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFFq7ZKMl/S4ZhUIzERApc6AKC9YjnE1LbaDHVi1GIObzwxbLLYiwCgmhDA
UKUfpk9I61+9rGL6XsL6Y/c=
=HIPu
-----END PGP SIGNATURE-----









__________________________________________________ _________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com

---------------------------(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