Hi all,

I'm trying to covert an old sqlanywhere database to firebird 1.5. The
current database schema uses several checks on colums.

I have the following problem, if there is a check on a column to check
if a value is eg 1 or 2 and the column can have null values,
sqlanywhere seems to accept null values, while firebird does not.
Firebird wants to enforce the check, and discards the "can be null" thing?

Is this correct? And is there some property that can disable this?

I could also change my schema to include null in all checks, but what
happens if I do that, and there is a column that has "not null"?

I hope this all makes a little sense.. This problem got me looking at
the databases for some time now..

TiA,

Alexander