Received: from huey.jpl.nasa.gov (huey.jpl.nasa.gov [128.149.68.100])
	by hub.org (8.10.1/8.10.1) with ESMTP id e63JRZS35342
	for <pgsql-interfaces@postgresql.org>;
	Mon, 3 Jul 2000 15:27:35 -0400 (EDT)
Received: from golem.jpl.nasa.gov (hectic-1 [128.149.68.203])
	by huey.jpl.nasa.gov (8.8.8+Sun/8.8.8) with ESMTP id MAA19840;
	Mon, 3 Jul 2000 12:27:29 -0700 (PDT)
Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1])
	by golem.jpl.nasa.gov (Postfix) with ESMTP
	id 4CB6F6F4F; Mon,  3 Jul 2000 19:30:31 +0000 (UTC)
Message-ID: <3960E9D7.531E9206@alumni.caltech.edu>
Date: Mon, 03 Jul 2000 19:30:31 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Organization: Yes
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14-15mdksmp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ken J. Wright" <ken@ori-ind.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: psql comment char??
References: <m139BCJ-000AXkC@druid.net>
	<00070312062700.13329@cncware.whidbey.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200007/14

> > 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.

                       - Thomas