André Knappstein wrote: > I am a bit worried, in any case, that you would expect different > results for the 2 cases, because in both cases the column literally > "is not nullable". > > Maybe what you want and need is a (new?) property "NOT_NULL_SET" which > could result to false for the column while "is_nullable" still _CAN_ > return false because of the underlying domain.
I think the problem here is all the double-negatives :-) So let's get this straight... A column is nullable by default, so if you don't specify anything at all, "is_nullable" should be 1. HOWEVER, if you specify "NOT NULL" on *either* the domain *or* the column, is_nullable should be 0. I hope we can all agree on that, at least... Now, whether that is actually the case, is something that I think we need to test. But I don't have a test environment on which I can test this right now :-) Dean. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
