> > > The NULL contraint: PostgreSQL only allows NOT NULL (NULL being
> > > the default). I altered the backend grammar for this one.
> >
> > Patch?
>
> OK. The patch to gram.y is almost certainly wrong: it's just a hack
> to get NULL acceptable---it should surely go in the same place as the
> check for NOT NULL.
Yes, and no. Putting the grammar where you did disallows any other
clauses, such as DEFAULT or CONSTRAINT, in the declaration. Trying to
put it in the proper place results in shift/reduce conflicts, since it
is ambiguous with other allowed syntax.
btw, afaik this is not SQL92 anyway...
> The floating point literal change is probably right, but it may break
> things (it may well cause more things to be regarded as floats than
> should be). Again, somebody who knows about this stuff definitely
> needs to check.
>
> I hope this helps all the same.
Yes it does! I've got a more general floating patch to apply, but would
not have done it without your prompting. Discussion and proposals are
how we progress. Good work.
Don't know how or if we want to proceed with a bare "NULL" clause.
Should we bother with a special case of _only_ NULL in a declaration, as
in Bruce's patch?
- Tom
