Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Geoff Tolley <geoff(dot)tolley(at)yougov(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped
Date: 2009-10-08 16:06:10
Message-ID: 25173.1255017970@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Shouldn't that be
> special_whitespace ({space}+|{comment}|{newline})

No, scratch that ... {comment} is the -- form of comment and the newline
is to terminate the comment.

The actual issue here seems to be that the whitespace productions only
deal with the -- form of comment, so that's the only kind you can embed
between sections of a string literal. This is okay per SQL92 but we
didn't upgrade it to SQL99, which appears to allow /* comments between
sections too.

Right offhand that looks like it would be *vastly* more work than it'd
be worth :-( --- there's no way to do /* comments without multiple
lexer rules.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Renner 2009-10-08 19:32:34 Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
Previous Message Kevin Grittner 2009-10-08 16:01:11 Re: BUG #5102: Silent IN (list of strings) failure to detect syntax error when list is linewrapped