On May 22, 11:10 pm, Scott Talsma <[EMAIL PROTECTED]> wrote: > Not sure if this will help, but I had a similar issue sometime last > year. I was able to confirm that the DB was changing via setData(), but > a subsequent read returned old data. Turns out that fourQ has some > built-in caching. Note that this only occurred when I did a getData(), > setData(), getData() all in a single request. > > I made a tweak for fourQ's getData() (optional param) overriding the > caching mechanism.
What would really help is having a test case for things that don't seem to work as expected so we can easily reproduce and fix these issues :) Do you have the change you made? There should be no need to tweak core for such a fundamental issue -- if its occurring it should be put right. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-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/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
