Re: pgsql error interpretation issue. solved - sort of...

i had my code tied up with the name of a file. when i
changed the name of the file, it didn't match anything
in the db and my code broke. when i used a correct
file name, all works well. looks like i have some
more error correction code to develop.

i'd still appreciate any insight into how to interpret
pgsql errors so i know where to attack my code,
though.

tia...

--- operationsengineer1(at)yahoo(dot)com wrote:

> i'm having the darndest time with some code... i
> had
> it working like a charm and then *improved* the code
> by apparently breaking it! -lol-
>
> anyway, i've gone back to an old rev of the code and
> i'm trying to tweak it to work. once i get it
> working, then i can *improve* the code once again
> without, hopefully, breaking the code again.
>
> anyway, pgsql is gave me the following error - one
> error for each of three tries to test the db.
>
> ERROR: syntax error at the end of input at character
> 69
> ERROR: syntax error at the end of input at character
> 70
> ERROR: syntax error at the end of input at character
> 69
>
> how can i interpret this error information so that i
> know where to look in my code to remove this error?
>
> tia...
>
>
>
> ____________________________________________________
>
> Yahoo! Sports
> Rekindle the Rivalries. Sign up for Fantasy Football
>
> http://football.fantasysports.yahoo.com
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com