From: Richard <blackw@sfu.ca>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Bug in parser?
Date: Mon, 07 Feb 2000 09:59:06 -0800
Message-ID: <389F07EA.6F39E687@sfu.ca> (raw)
References: <389B70B7.D428C352@sfu.ca>
<389B88ED.DF613747@austin.rr.com>
<389EF2A7.565769D0@sfu.ca>
<20000207111759.D24062@rice.edu>
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!)
Thanks for your help. And thanks to Axel too, who e-mailed me directly
suggesting the same thing.
Cheers,
Richard
"Ross J. Reedstrom" wrote:
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: blackw@sfu.ca
Subject: Re: [INTERFACES] Bug in parser?
In-Reply-To: <389F07EA.6F39E687@sfu.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox