From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: Ken J. Wright <ken@ori-ind.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: psql comment char??
Date: Mon, 03 Jul 2000 15:41:56 -0400
Message-ID: <20206.962653316@sss.pgh.pa.us> (raw)
In-Reply-To: <3960E9D7.531E9206@alumni.caltech.edu>
References: <m139BCJ-000AXkC@druid.net>
<00070312062700.13329@cncware.whidbey.com>
<3960E9D7.531E9206@alumni.caltech.edu>
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
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: tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu, ken@ori-ind.com
Subject: Re: psql comment char??
In-Reply-To: <20206.962653316@sss.pgh.pa.us>
* 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