Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.10.1/8.10.1) with ESMTP id e63JgTS71706
	for <pgsql-interfaces@postgresql.org>;
	Mon, 3 Jul 2000 15:42:29 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id PAA20209;
	Mon, 3 Jul 2000 15:41:56 -0400 (EDT)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: "Ken J. Wright" <ken@ori-ind.com>, pgsql-interfaces@postgresql.org
Subject: Re: psql comment char?? 
In-reply-to: <3960E9D7.531E9206@alumni.caltech.edu> 
References: <m139BCJ-000AXkC@druid.net>
	<00070312062700.13329@cncware.whidbey.com>
	<3960E9D7.531E9206@alumni.caltech.edu>
Comments: In-reply-to Thomas Lockhart <lockhart@alumni.caltech.edu>
	message dated "Mon, 03 Jul 2000 19:30:31 -0000"
Date: Mon, 03 Jul 2000 15:41:56 -0400
Message-ID: <20206.962653316@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200007/15

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>>>> I would call those the alternate forms.  The canonical (SQL) way is
>>>> -- This is a comment
>> Is this part of the SQL-92 spec?

> This is the *only* comment delimiter defined in the SQL92 spec. The "/*
> .. */" form is present in several database products since a
> block-delimited comment is very useful.

Note that SQL99 added /* ... */ comments.

We are not fully compliant with SQL99's comment specifications, since it
specifies that /* ... */ nest, which is a tad hard to implement in a
finite-state lexer :-(

			regards, tom lane