Fabien COELHO <[EMAIL PROTECTED]> writes:
>> In particular, we determined that the appropriate place for this sort of
>> thing is on the client side, not in the backend.
> The current status of clients is that none of those I use will report
> anything useful.
So fix the clients. We have been th
Fabien COELHO <[EMAIL PROTECTED]> writes:
> (1) Lexical/syntax error source localisation
> An extract of the offending source must be shown if possible along syntax
> error messages.
You would do well to go to the archives and read some of the previous
discussion of these issues. In particular,
Dear Hackers,
Motivation
--
As a basic user of postgresql, I've been quite disappointed by the lack of
help provided by postgresql error messages dealing with syntax and
semantical errors, especially in long sql statements:
ERROR: syntax error at or near "(" at character 326
T
