On 1/10/08, VS-Polis <[EMAIL PROTECTED]> wrote:
> If the database column itself is set to "not null" or if this column is
> part of the primary key, it returns is_nullable as correct value "1" resp.
> "true". If the database column is defined via domain and the domain is set
> to "not null", the column value "is_nullable" nevertheless returns
> incorrectly "1" resp. "true", but not the expected correct value "0" resp.
> "false".
This is right, imo. The NOT NULL work like this:
1. If the domain is not null > not null = true
2. If the domain isn't not null, look at the column definition; if the
column definition is not null > not null = true
3. Othervise.
So you cannot override not null to null on not null domain.
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
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
