From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Axel at ansonic <goddyna@ansonic.com.au>
Cc: pgsql-interfaces@postgreSQL.org, "Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>
Cc: blackw@sfu.ca
Subject: Re: [INTERFACES] Bug in parser?
Date: Tue, 08 Feb 2000 06:06:51 +0000
Message-ID: <389FB27B.1F9702BD@alumni.caltech.edu> (raw)
References: <NABBLEOMMPNHHMBPOBPFIENAFFAA.goddyna@ansonic.com.au>
<27734.949981876@sss.pgh.pa.us>
> My question to the lex gurus: why doesn't this rule simply read
> xqcat {quote}{space}*{quote}
> considering that both \r and \n are members of {space}? In fact,
> shouldn't xqdouble and xqcat be combined and defined as above?
> Unless lex has some weird built-in special treatment of \n,
> I don't see why we need to call it out explicitly.
>
> Similar comments apply to xbcat and xhcat --- and I'm kind of
> wondering about xqliteral, xcline, and xcstop, all of which seem
> to accord undeserved special status to \n ...
Pretty sure that the SQL92 rules for the "string across lines" is more
restrictive than just allowing spaces between double quotes; you
actually need something close to a line break.
select * from "T1" "A1";
would do horrible things if I interpret your suggestion correctly.
But perhaps a somewhat more general rule would work, allowing \r \c
and \n as line break characters??
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
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: lockhart@alumni.caltech.edu, tgl@sss.pgh.pa.us, goddyna@ansonic.com.au, reedstrm@wallace.ece.rice.edu, blackw@sfu.ca
Subject: Re: [INTERFACES] Bug in parser?
In-Reply-To: <389FB27B.1F9702BD@alumni.caltech.edu>
* 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