Re: [INTERFACES] Bug in parser?

Richard -
I recently tripped over some whitespace sensitivity (that shouldn't be
there!) involving line-endings in queries. Could you try your UPDATE all
on one line, and see if that solves it? I haven't been able to replicate
my problem with my current set up (in order to file a bug report). It
originally happened with a demo system we had set up at a meeting. Once
we got back to the office, everything worked fine, of course!

We got the same sort of 'paser error at or near ""' line in the log,
but when I looked with the right editor, I say that there was a control
character (either ^M or ^R, can't remember which) between the quotes.

Ross
--

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

On Mon, Feb 07, 2000 at 08:28:23AM -0800, Richard wrote:
> Thanks, but nope... didn't help.
>
> Cheers,
> Richard
>
> Ed Loehr wrote:
> >
> > Richard wrote:
> > >
> > > UPDATE ActiveUser SET status=-1
> > > WHERE (datetime('today'::date, 'now'::time) - lastrequest) >
> > > timespan('10 minutes'::reltime)
> > >
> > > parser: parser error at or near ""
> > >
> > A guess: try spaces around your '=' operator...that one sometimes
> > doesn't like being crowded...
> >
> > Cheers,
> > Ed Loehr
>
> ************
>