Hi Laurent!
As I stated, I get the error messages when opening the edit grid with a
filter in pgAdmin or when running SQL from psql (standard command line
interface of PG). In the SQL query dialogue window of pgAdmin I only get
the error code. This problem has been reported shortly after release of
v1.6.2 and (I think, correct me if I'm wrong) is fixed already. But we
have to wait for the next release.
My report is concerned with the crashing, which is a more serious problem.
Regards
Erwin
[EMAIL PROTECTED] wrote:
Hello Erwin,
I am interested in the part "I get an error message with only the error code".
I have the same problem, however in the rest of your message you do have an error message with the error code
" FEHLER: Fehler »Syntaxfehler« bei »loc«
SQL state: 42601
Character: 1"
How do you achieve this ?
My problem is that, if my database is in UTF-8, I will not get any error
messages, just the code.
Is that the same for you ? Have you found a solution to have an error message ?
So far we have not been able to reproduce this error: it seems its due to my PG
server configuration (Ubuntu with French locale), other configurations
(including on WinXP machine) work fine.
Cheers,
[EMAIL PROTECTED]
The Computing Froggy
----- Message d'origine ----
De : Erwin Brandstetter <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Mercredi, 21 Février 2007, 2h06mn 21s
Objet : [pgadmin-support] Crashing v1.6.2 with a syntax error
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.2 rev: 5837, client Win XP, host Debian Sarge,
PG 8.1.4. / Debian Etch, PG 8.2.1.
I have found a 'reliable' way to crash pgAdmin. Look at the following query:
select * from loc where loc like 'a%' loc = 'b';
Note the syntax error: "and" is missing in the WHERE clause. If I run
this from the SQL query dialogue window I get an error message with only
the error code - but that has been reported before.
FEHLER: Fehler »Syntaxfehler« bei »loc«
SQL state: 42601
Character: 1
However, if I open the edit grid with a filter and enter the faulty
WHERE clause, pgAdmin crashes.
I have run tests with a variety of tables and operators in PG 8.1.4 and
PG 8.2.1. Any of the following WHERE clauses triggers a crash.
fld1 like 'a%' fld2 = 'b'
fld1 = 'a%' fld2 = 'b'
fld1 = 'a%' fld1 = '%a%'
...
The "essential" part ist the "%" at the end of the first string.
An observation I have made along the way:
Look at the error message I get from pgAdmin for the following WHERE clause:
loc = '%a' loc = ''
Note that the % is in front this time (does not trigger a crash).
An error has occurred:
FEHLER: Fehler >>Syntaxfehler<< bei >>b<<
Line 1: EXPLAIN SELECT * FROM loc WHERE loc = '0x1.1f9d8ap-997' loc = ''
^
The string containing the character "%" is scrambled in a weird way. The
caret in the next line points to a seemingly random position.
If I run it from psql, I get a similar error message. Only the string is
not scrambled, and the caret is in a reasonable position.
event=# select * from loc where loc = '%a' loc = '';
FEHLER: Fehler »Syntaxfehler« bei »loc« at character 36
ZEILE 1: select * from loc where loc = '%a' loc = '';
^
I have tried to switch the "user language" in the pgAdmin options from
English to German. To no effect.
It might have to do with locales. From my postgresql.conf:
lc_messages = '[EMAIL PROTECTED]'
I have tried changing it to:
lc_messages = 'C'
After that the error message was scrambled differently:
loc = '%a' loc = ''
An error has occurred:
ERROR: syntax error at or near "loc"
LINE 1: EXPLAIN SELECT * FROM loc WHERE loc = '0x1.518a0fp-1002' loc
= ''
^
But it crashes just as well.
loc = 'a%' loc = ''
Regards
Erwin
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
___________________________________________________________________________
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 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
