Re: Data integrity and sanity check

> BTW.  There are good reasons sometimes for having data that violates
> current constraints.  The top of a tree may have a static record with
> a null parent.  The NOT NULL constraint added after this entry (via
> alter table add constraint) should not affect the static record, so
> unless you know your data quite well this type of tool wouldn't be
> particularly useful anyway.

As far as I am aware, there is no alter table add constraint syntax for
NOT NULLs atm.  I've submitted a patch that allows alter table/alter
column set/drop not null though.

Chris