RE: [INTERFACES] Bug in parser?

Hi there,

For ones I can say I can (reproduce an error, it seems to be my talent)

I did write some cgi code in c with a select statement in notepad to be
executed with PQexec.
I broke the line with enter (entering asci char 13 & 10)
then tranfered the code to unix
reedited the file, take the line break out of it with one backspace (taking
out asci char 10)
Note asci char 13 still lives in the file, and is invisible.
Compiling is ok.
After executing the cgi PQtrace tells me:"ERROR: parser: parse error at or
near ""

regards Axel

> -----Original Message-----
> From: owner-pgsql-interfaces(at)postgreSQL(dot)org
> [mailto:owner-pgsql-interfaces(at)postgreSQL(dot)org]On Behalf Of Ross J.
> Reedstrom
> Sent: Tuesday, 8 February 2000 5:46
> To: Richard
> Cc: pgsql-interfaces(at)postgreSQL(dot)org
> Subject: Re: [INTERFACES] Bug in parser?
>
>
> On Mon, Feb 07, 2000 at 09:59:06AM -0800, Richard wrote:
> > Bingo!
> >
> > I erased the SQL command and typed it on one line. Works find. Broke
> > it up again with linefeeds. STILL WORKS!
> >
> > Now I wish I had commented-out the original command rather than
> > replacing it, as now I don't know what the rogue character was!
> > Grrrrrr! (I need more sleep!)
>

If you don't have much time to sleep, sleep faster...?

> Ah, this means you can't reproduce it either? I was hoping you might
> be able to get a reproducible case, so we could get this bug stomped for
> 7.0 beta. Any chance the query was coming from a file that might have been
> edited from a Win32 mount/share? I think that's what triggered it for us.
>
> Ross
>
> >
> > Thanks for your help. And thanks to Axel too, who e-mailed me directly
> > suggesting the same thing.
> >
> > Cheers,
> > Richard
> >
>
> --
> Ross J. Reedstrom, Ph.D., <reedstrm(at)rice(dot)edu>
> NSBRI Research Scientist/Programmer
> Computer and Information Technology Institute
> Rice University, 6100 S. Main St., Houston, TX 77005
>
> ************
>