Re: [HACKERS] Subselects and NOTs

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