by default.
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
- Original Message -
From: will trillich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 27, 2001 12:56 AM
Subject: Re: [GENERAL] last comma inside
On Sunday 22 April 2001 10:21, you wrote:
however, this seems like a reasonable idea that would not introduce
any major problems. I have no objections, if someone wants to submit
a grammar patch.
regards, tom lane
Please don't. IMHO This would be an unnecessary
Is it against the SQL standard to accept a trailing comma in a table
declaration?
CREATE TABLE "currency" (
currency_id varchar(3),
rate float, BOOM! parse error
);
As in perl, it would make life easier to simply ignore/accept a trailing
comma on table declarations.
On Sun, 22 Apr 2001, Louis-David Mitterrand wrote:
Is it against the SQL standard to accept a trailing comma in a table
declaration?
Yes it is.
CREATE TABLE "currency" (
currency_id varchar(3),
rate float, BOOM! parse error
);
As in perl, it would make life
Louis-David Mitterrand [EMAIL PROTECTED] writes:
Is it against the SQL standard to accept a trailing comma in a table
declaration?
Yes ...
CREATE TABLE "currency" (
currency_id varchar(3),
rate float, BOOM! parse error
);
As in perl, it would make life
Tom Lane wrote:
Louis-David Mitterrand [EMAIL PROTECTED] writes:
Is it against the SQL standard to accept a trailing comma in a table
declaration?
Yes ...
CREATE TABLE "currency" (
currency_id varchar(3),
rate float, BOOM! parse error
);
On Sun, Apr 22, 2001 at 07:44:46PM +0100, some SMTP stream spewed forth:
Tom Lane wrote:
Louis-David Mitterrand [EMAIL PROTECTED] writes:
Is it against the SQL standard to accept a trailing comma in a table
declaration?
Yes ...
CREATE TABLE "currency" (
