>Jim,
>
>
>The problem w/any data exchange language is your potentially exchanging data
>between 2 different languages that aren't really compatible. For example,
>ColdFusion has no concept of null data. JavaScript actually has two
>different states of variables without values--undefined and null (which are
>completely different beasts in JavaScript.)
Thanks - I'm actually not looking to really change the spec but to get some
ideas for how others are already handling the issue.
It's not so much a problem of "maintaining null" tho' - I really
(unfortunately) "get" that problem. It's a problem of untyped data in a typed
field. Although database support null in any column most languages don't (you
can't have a "null" boolean in JavaScript, CF or Java for example but you can
in a database.)
So how to best translate that - any data exchange will have to deal with that.
Personally I'm leaning towards saying if you can have three values ("true",
"false" or "null") then it's not really a boolean. Use a string field, dummy.
This sorta works but causes havok for dates (which are left as strings and then
need to be manually conveted to "real" dates later).
I'm playing with WDDX now to see how the JS and CF versions react to this...
but it would be nice to have some other input.
Jim Davis
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227098
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
