From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jan Wieck <wieck(at)debis(dot)com>, goran(at)kirra(dot)net, pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] NULL |
Date: | 1999-11-30 03:13:59 |
Message-ID: | 199911300313.WAA25238@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> wieck(at)debis(dot)com (Jan Wieck) writes:
> > I can't see any shift/reduce conflicts if I place a
> > | NULL_P
> > case into the ColConstraintElem: definition right between the
> > | DEFAULT b_expr
> > and
> > | NOT NULL_P
> > cases. Could it be that this reason is out of date?
>
> Could be. I remember tweaking the ColConstraint grammar to avoid
> shift-reduce conflicts with NOT NULL, and it might be that that got
> rid of the problem with NULL as well.
>
> It's still not legal under the SQL92 spec, though, and I'd hate to see
> us give up anything else in order to allow a content-free NULL spec to
> be added...
OK, I assume we are going to dis-allow NULL as a column constraint. We
could allow it but emmit a notice.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Thilo Mezger | 1999-11-30 08:07:35 | unixtime -> datetime |
Previous Message | Alexey V. Meledin | 1999-11-29 17:00:32 |