this might explain the problem better... 1) in my handler, i'm creating a transfer object from event scope attributes. 2) i pass this transfer object to my manager 3) my manager evaluates if any of the getters have values 4) if my manager sees a default value for numerics or uuid ... it ignores it. 5) if my manager sees a non default value, it does stuff with it.
the problem is that anything other than 'true' or 'false' used to setBooleanField() throws an exception with a type error (which is understandable), but because transfer is including the field in the where clause (because it's populated by transfer as false even if i don't populate it), and i can't setBooleanField() to anything other than a boolean value, i'm unable to truly identify if my handler is asking for 'true', 'false', 'true and false', or if the 'false' is just a result of transfer's default population of the property. i don't know how this would be resolved other than getting rid of the typing entirely for bit values and not setting the default at all. for now, i've just started changing my boolean fields to varchar in mysql, and to 'string' types in my transfer config. then i can at least pass a "" value into my setLoginRequired() and it won't get included into the where clause, giving me 'true and false' instead of 'false' as default. -- Jim Rising Serial Entrepreneur Software Engineer Web Developer "Knowledge work requires both autonomy and accountability." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
