An easier solution is to clone() your Transfer object before you populate it. Then the dirty data never gets into the cache.
Sent from my iPhone On 2010-08-17, at 7:53 PM, pedrobl <[email protected]> wrote: > > OK, after reading again the documentation on caching, I thought it'd > smart to discard the invalid object from the cache. Simple. > > It's probably in the documentation... but I'm fond of learning by > making mistakes... very fond of, apparently, :) > > Pedro. > > -- > 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
