Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA39049 for ; Tue, 8 Feb 2000 02:06:02 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id HAA04464; Tue, 8 Feb 2000 07:13:31 GMT Sender: lockhart@hub.org Message-ID: <389FC21B.6B0B3012@alumni.caltech.edu> Date: Tue, 08 Feb 2000 07:13:31 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: Axel at ansonic , pgsql-interfaces@postgreSQL.org, "Ross J. Reedstrom" , blackw@sfu.ca Subject: Re: [INTERFACES] Bug in parser? References: <27734.949981876@sss.pgh.pa.us> <389FB27B.1F9702BD@alumni.caltech.edu> <405.949992133@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > * I see that the spec allows comments between segments of a string > literal. This works in current code: > regression=# select 'a string' -- zzz > regression-# ' literal'; > ?column? > ------------------ > a string literal > (1 row) > but I'm durned if I see where that behavior is implemented. > Do you? It used to be implemented in psql, and might still. Looks to me that scan.l might be missing this case (which presumably you are thinking also). I'm still recalling the "line break" reasoning for concatenating literals, but maybe that was just an example from the Date book rather than the entire rule. - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California