>You're suggesting the user change his application data rules because the language doesn't support nullable booleans.
I am certainly not suggesting that a user should change his application data rules. I am trying to point out that if you want a value that can be 'not set', 'true' or 'false you should not look to boolean. I might be mistaken here. But to come back to the quoted comment, my suggestion is to use another data type. If the data does not exist natively you could create it. There is a small chapter in the Programming Actionscript pdf called The AS3 namespace. I'm not sure but this chapter might help in with this subject though, who knows. Anyway, this discussion seems at it's end and I wish merelypixels good luck with solving his problems. Greetz Erik On 9/19/07, Samuel R. Neff <[EMAIL PROTECTED]> wrote: > > 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 > > > ------------------------------------------- >
