Hi,

> > I've just tested with the latest FB release and IB too, just modifying

the

> RDB$NULL_FLAG does the trick. But, when setting it to 0 or NULL, the
> constraint in rdb$relation_constraints and rdb$check_constraints doesn't

get

> dropped automagically... Is this as expected or not?
>
> Those inconsistencies are expected as you are observing a constraints

system

> mounted over an older constraints system, same as the SQL security model

was

> mounted over the GDML, ACL-based security model. It would be nice to clean
> the house a bit. Maybe you coud fill a request for enhancent at SF.

But what should be the result - the RDB$NULL_FLAG column that has the last
say or the records in the system tables. As for NOT NULL constraints in the
system tables, the RDB$CHECK_CONSTRAINTS table holds the column name of the
NOT NULL constraint the the _RDB$TRIGGER_NAME_ column - duh, I wouldn't
expect that :)

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."