--- In [email protected], "Charlie Hubbard" <[EMAIL PROTECTED]> wrote: > > Ok thanks Johannes. Very good point. Number's can't really be NULL either. > However, it just so happens that NaN is interpreted as NULL to the datatype > conversion layer in AIR and it just happens to work out. Maybe this slight > difference between NaN and NULL doesn't really matter, but it's good to know > that it exists. > My temptation is to write a real object that encapsulates int's as a true > Object data type that can really be NULL, but the draw back here is that it > would be incompatible with AIR's handy databinding (itemClass on > SQLStatement since AIR will convert database integers to Numbers instead of > my abstraction). > > I guess more investigation is needed in these matters.
I don't see why you can't just use myInt==undefined?null:myInt; That also avoids the possibility of strange rounding errors you set yourself up for when you use Number instead of int. But hey maybe there's something special about sqlLite's version of SQL that makes it impossible to perform evaluations like that in the statement...?
