I think my original patch about NOT NULL constraint allows this type of
construction. However, thinks have changed in the parser since I made
this patch, and now seems that a construction like
CREATE TABLE a (b int constraint not_null NOT NULL)
is now valid (I only saw gram.y - maybe I'm wrong). I can make the
patches to allow NULL, but I only want a litte help: is the name of this
type of constraint beeing saved anywere?
Robson.
Bruce Momjian wrote:
>
> Added to TODO.
>
> > Here's my output. BTW, this reminds me of a small request (perhaps I
> > will write a patch for it myself). In Postgres, a column can be
> > designated "not null", the default being to allow nulls. In the
> > default Sybase configuration, it is the other way around. In the
> > interest of writing cross database compatible code, I try to always
> > call out columns as either "null" (nulls allowed), or "not null"
> > (nulls not allowed). Unfortunately, Postgres does not support this
> > (Please forgive me if this has been added recently, as I have been too
> > busy to try out the latest code).
> >
> > In short, it would be nice if Postgres would take "null" as a type
> > specifier as well as "not null".
>
> --
> Bruce Momjian
> maillist@candle.pha.pa.us
