| Subject | Re: [firebird-support] Re: Domain not null, foreign key nullable? |
|---|---|
| Author | Mark Rotteveel |
| Post date | 2011-06-12T14:04:50Z |
On 12-6-2011 15:05, firebirdsql wrote:
restriction. You can only apply more restrictive constraints when
defining a column based on a domain, not less restrictive.
In this case you will need to define your domain without the NOT NULL
constraint and apply the NOT NULL definition for columns that should not
allow null.
--
Mark Rotteveel
> I use the domain for foreign keys which sometimes can be nullable. The column's nullable value (if one is set) should therefore override the domain's nullable value.No it shouldn't: the domain is more restrictive so you can't lessen the
restriction. You can only apply more restrictive constraints when
defining a column based on a domain, not less restrictive.
In this case you will need to define your domain without the NOT NULL
constraint and apply the NOT NULL definition for columns that should not
allow null.
--
Mark Rotteveel