Hi group, We recently hit some issues with our application to do with clustering and Transfer caching throwing strange behaviour. Seems to be an issue that's well documented online with blogs etc. but the fix that my colleagues put in place while I was on holiday was to switch Transfer's caching completely off.
It seems to have fixed the problems in the application but we've now got this side affect of some Unit Tests and Developer clean up tools failing ( errors relating to foreign key constraint spring to mind that actually don't exist anymore when looking at the DB ). My question was, apart from performance, what kind of issues might we expect from taking this action? Is this really a big no-no? The application itself doesn't do much heavy database saving / deleting work apart from at key points the user hits. Apart from that most of it is session driven objects. Thanks for any advice, James -- 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
