awesome. that worked. showing my inexperience with booleans here... but i never would have thought of a -1 for a boolean null. :)
thanks Mark! -jim On Aug 27, 11:34 am, Mark Mandel <[email protected]> wrote: > Try using -1 for your boolean null value. > > Mark > > On Fri, Aug 28, 2009 at 12:45 AM, Jim Rising <[email protected]>wrote: > > > > > tried that: > > > can't cast String [NULL] to a value of type [boolean] > > > bummer. :( > > > -- > > Jim Rising > > Serial Entrepreneur > > Software Engineer > > Web Developer > > > "Knowledge work requires both autonomy and accountability." > > > On Wed, Aug 26, 2009 at 8:24 PM, Bob Silverberg > > <[email protected]>wrote: > > >> OK, well if they're nullable you could use configure() to default the > >> property to NULL, and then check for nulls in your method rather than > >> checking for "". Does that make sense? > > -- > E: [email protected] > T:http://www.twitter.com/neurotic > W:www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
