From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Sean Chittenden" <sean(at)chittenden(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Adding // comments (ANSI??)... |
Date: | 2003-02-05 02:03:07 |
Message-ID: | GNELIHDDFBOCMGBFGEFOGEGDCFAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
As far as I'm aware, MySQL is the only database that supports '//' as a
comment, and they made it up out of whole cloth...
ANSI _C_ perhaps...
Chris
> -----Original Message-----
> From: pgsql-patches-owner(at)postgresql(dot)org
> [mailto:pgsql-patches-owner(at)postgresql(dot)org]On Behalf Of Sean Chittenden
> Sent: Wednesday, 5 February 2003 7:22 AM
> To: pgsql-patches(at)postgresql(dot)org
> Subject: [PATCHES] Adding // comments (ANSI??)...
>
>
> I just had a friend over at EDS ask me if PostgreSQL supported //
> comments. It didn't, so I put together a patch for them so that they
> could retain compatiblity across the databases they work on.
>
> I didn't think much of it until I took a gander at the crash-me page
> on mysql.com and I couldn't find a single vendor that supports //
> comments, but it did list // as an ANSI supported comment. ::shrug::
> I don't have a copy of the spec, so someone more knowledgable in that
> area will have to speak to this or whether or not support for // is
> even wantd, but, here's the patch and regression tests. -sc
>
> --
> Sean Chittenden
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-02-05 02:36:26 | Re: Adding // comments (ANSI??)... |
Previous Message | Sean Chittenden | 2003-02-04 23:21:35 | Adding // comments (ANSI??)... |