From: | "Zeugswetter Andreas" <andreas(dot)zeugswetter(at)telecom(dot)at> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | <hackers(at)postgresql(dot)org> |
Subject: | Re: FORMAL VOTE ON =- and similar |
Date: | 2000-06-12 14:46:51 |
Message-ID: | 00da01bfd481$f17c7b40$e823080a@sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Can someone comment on this? Add to TODO?
No.
> > On Fri, 17 Mar 2000, Thomas Lockhart wrote:
> > >Actually, I'd suggest we *remove* the "//" comment delimiters
> > >altogether. We always had the "--" SQL92 delimiter, I added the "/*
> > >... */" so we could get a block delimiter of some sort (it is the same
> > >aas in Ingres). I don't know what other DBMSes do, and we could define
> > >something else instead if SQL3 or some other convention offers a
> > >strong reason.
> >
> > I think the standard specifies the curly brackets as comment block characters.
wrong, I'm sorry for the misinformation.
> > I checked, and we do not have them :-(
> >
> > Example:
> > select { this is a comment } * from pg_class;
> >
> > Most (all that I know) other DB's have them
It turns out I was always beleiving it to be so, but it isn't.
The {} are an Informix'ism and thus not worth implementing.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-12 14:50:46 | Re: Gripe: working on configure now requires Automake installed locally |
Previous Message | Mike Mascari | 2000-06-12 14:33:21 | Re: Proposal: TRUNCATE TABLE table RESTRICT |