Good stuff, I thought I'd just post that for other peoples reference.

I've not had much luck with Railo and Transfer, even with the WasNull fix I get 
a chain of other problems, which is a shame. But as you say, for legacy apps I 
can't complain too much :-)

Thanks.

Rob

On 10 Oct 2011, at 10:43, Sergii Galashyn wrote:

> 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,
>> 
>> Thanks for posting this work around.
>> 
>> People who impalement this will still need to do lots of testing on their 
>> app, as although no exceptions were thrown by older versions of Railo the 
>> NULL functionality of transfer was _not_ working properly.
>> 
>> So, even with this fix in place, people will likely get unexpected, 
>> differing behaviour to what they were getting with earlier versions of Railo.
>> 
>> Thanks.
>> 
>> Rob
>> 
>> On 10 Oct 2011, at 10:34, Sergii Galashyn wrote:
>> 
>>> Just to have this discussion complete (kind of) in case someone finds it 
>>> with same issue, here's the workaround for Railo 3.3 users.
>>> 
>>> Edit /com/sql/SQLValue.cfc
>>> 
>>> Replace 
>>> 
>>> if(isQueryCellNull(arguments.query, arguments.property.getColumn(), 
>>> arguments.query.currentRow))
>>> 
>>> with
>>> 
>>> if(!isDefined("value"))
>>> 
>>> -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 [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
>> 
>> -- 
>> 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 [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
> 
> 
> -- 
> 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 [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

-- 
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 [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

Reply via email to