On Thu, May 11, 2006 at 09:39:59AM -0500, Tony Caduto wrote:
> Tom Lane wrote:
> >
> >We have actually removed the "at character N" bit from the default message
> >format in CVS
> >
> Tom,
> What will the error format be for 8.2? Since the char number has been
> removed, what will it show?
>
Tony Caduto <[EMAIL PROTECTED]> writes:
> I guess I didn't know there was a error-position field returned, I have
> been parsing out the "at character xx" to get the char number.
> Do you know offhand if there is the error-position field is discussed in
> the docs anywhere?
See PQresultErrorFie
Hi Tom,
I guess I didn't know there was a error-position field returned, I have
been parsing out the "at character xx" to get the char number.
Do you know offhand if there is the error-position field is discussed in
the docs anywhere?
Not a C guy but possibly?
http://www.commandprompt.co
On Thu, May 11, 2006 at 10:56:20AM -0400, Tom Lane wrote:
> We still include "at character N" if the message is written to the
> server log, but the "primary message text" field of the error report
> sent to the client doesn't have it any more.
Will the text returned by PQerrorMessage still includ
In CVS tip you just see
regression=# select 1 2;
ERROR: syntax error at or near "2"
LINE 1: select 1 2;
^
regression=#
We still include "at character N" if the message is written to the
server log, but the "primary message text" field of the error report
sent to the client does
Tony Caduto <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> We have actually removed the "at character N" bit from the default message
>> format in CVS
>>
> What will the error format be for 8.2?
In CVS tip you just see
regression=# select 1 2;
ERROR: syntax error at or near "2"
LINE 1: selec
Tom Lane wrote:
We have actually removed the "at character N" bit from the default message
format in CVS
Tom,
What will the error format be for 8.2? Since the char number has been
removed, what will it show?
Line number?
Thanks,
--
Tony Caduto
AM Software Design
http://www.amsoftwared
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 11 May 2006 15:00
> To: Anastasios Hatzis
> Cc: pgsql-general@postgresql.org; pgadmin-hackers@postgresql.org
> Subject: Re: [GENERAL] Debugging SQL queries
Anastasios Hatzis <[EMAIL PROTECTED]> writes:
> I have sometimes very long queries, for example in setup-purposed sql
> file where plenty of tables of a new database are created in a single
> transaction. 600 lines of code or more is common. Sometimes, while
> developing, an error may appear aft
On 5/11/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
From my point of view, more important problem is that log doesn't help
to find the query (in other words, log message doesn't show context)
Yes it does.. but it depends on your logging setup.
in psql:
test=# blah;
ERROR: syntax error
From my point of view, more important problem is that log doesn't help
to find the query (in other words, log message doesn't show context)
On 5/11/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
Anastasios Hatzis <[EMAIL PROTECTED]> writes:
> My problem is that I don't know where the given cha
Douglas McNaught wrote:
Emacs has the "goto-char" function and runs on Windows, so you could
use that (there are probably other editors with this feature as
well)..
Doug, thank you. I will use it. - Ha, I never thought I will ever use
legendary Emacs. Probably I will even become an entry-clas
Anastasios Hatzis <[EMAIL PROTECTED]> writes:
> My problem is that I don't know where the given character number is
> inside the query/file. I can search in my code editors (e.g. those of
> Eclipse IDE) for line number + character number in given line
> number... but I can not search for an overal
I have sometimes very long queries, for example in setup-purposed sql
file where plenty of tables of a new database are created in a single
transaction. 600 lines of code or more is common. Sometimes, while
developing, an error may appear after submitting such a query for
testing purposes via
14 matches
Mail list logo