The default value and NULL are very different things. NULL means the data point is not known or not set yet. If you just use the default values then there is no way to differentiate between a 0 value that is there because it happens to be the default or a 0 value that is correctly zero based on user input or application rules. And setting things to not nullable in the database only works if your data truly is not nullable. You're suggesting the user change his application data rules because the language doesn't support nullable booleans. Shouldn't the application rules dictate what the application does and not the language the application happens to be programmed in? :-) Sam
------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of EECOLOR Sent: Wednesday, September 19, 2007 2:30 AM To: [email protected] Subject: Re: [flexcoders] nulling primitive data types These are the simple types and their default values: uint - 0 int - 0 Number - NaN String - null Boolean - false I still do not get your problem. In your database a representation of a boolean would be a bit type. Which means that it's either true or false. You could look at your problem in antother way. A boolean should have two values, that's what the term suggests. Your database however adds another value: NULL. This is kinda strange. You could set the field in your database to NOT NULLABLE and declare a default value. The field in the database should represent something that is either true or false. I hope this last bit makes any sense, quite hard to tell in a language which is not your own. Greetz Erik
