Yes, you are correct. That's why I've called this "workaround", not
"solution" :) Nulls were not working in Railo any way, so our aim was to make Transfer just work with new Railo as previously. Personally for me it seems to work fine, which is good enough for legacy apps. Thanks, -sg 10.10.11 12:37, Robert Rawlins написав(ла): Hi SG,-- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en |
- [transfer-dev] Fixing wasNull() in Railo (3.3.0.027) Sergii Galashyn
- Re: [transfer-dev] Fixing wasNull() in Railo (3.3.0.0... Robert Rawlins
- [transfer-dev] Re: Fixing wasNull() in Railo (3.3.0.0... Sergii Galashyn
- Re: [transfer-dev] Re: Fixing wasNull() in Railo ... Robert Rawlins
- Re: [transfer-dev] Re: Fixing wasNull() in Ra... Sergii Galashyn
- Re: [transfer-dev] Re: Fixing wasNull() i... Robert Rawlins