| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | wieck(at)debis(dot)com (Jan Wieck) |
| Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian), goran(at)kirra(dot)net, pgsql-sql(at)postgreSQL(dot)org |
| Subject: | Re: [SQL] NULL |
| Date: | 1999-11-16 00:50:16 |
| Message-ID: | 19817.942713416@sss.pgh.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...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 1999-11-16 03:19:13 | Re: [SQL] how can tell if a column is a primary key? |
| Previous Message | Jan Wieck | 1999-11-15 23:48:21 | Re: [SQL] NULL |