Bug#257117 Re: Error messages in SQL Query window
От | Raphaël Enrici |
---|---|
Тема | Bug#257117 Re: Error messages in SQL Query window |
Дата | |
Msg-id | 40E67656.8020208@club-internet.fr обсуждение исходный текст |
Ответ на | Re: Error messages in SQL Query window (Andreas Pflug <pgadmin@pse-consulting.de>) |
Ответы |
Re: Bug#257117 Re: Error messages in SQL Query
|
Список | pgadmin-hackers |
Hi Andreas, hope I won't mess you with a known one... Andreas Pflug wrote: > Raphaël Enrici wrote: > >> can one of you confirm that error messages displayed under the SQL >> query window are generated by the PostgreSQL backend and not by >> pgAdmin III ? > > > That's correct, everything in the message tab and in case of problems > in the status line is from the backend. Ok, Ricardo Pérez López (CCed) reported a strange behaviour about two days ago concerning error messages not displayed at all while using a es_ES@euro locale under debian. The detail of the bug can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257117 The problem appears while playing with locales and trying to query a non existent table: select * from doesnotexist; in the SQL Query window. Here is where I am with it: a) put lc_messages=es_ES@euro in postgresql.conf export LC_ALL=POSIX ; /etc/init.d/postgresql restart open a new terminal without changing anything to you normal locale settings, launch pgadmin3 and retry your test... The error message should appear correctly in spanish. b) leave es_ES@euro in postgresql.conf then do this export LC_ALL=es_ES@euro ; /etc/init.d/postgresql restart open a new terminal without changing anything to you normal locale settings, launch pgadmin3 and retry your test... The error message *DOES NOT* appear correctly in spanish. What makes me think it is not a backend bug is that everything runs well if I do the same thing with psql (I mean I have the expected error message in Spanish). The problem seems to occur only in pgAdmin III. I've tried a recent snapshot with no luck. Nothing particular in pgAdmin3 logs. It seems something is broken somewhere but I can't discover what and where. Can someone reproduce this on another distro ? Any further idea ? Regars, Raphaël
В списке pgadmin-hackers по дате отправления: