I have a case where I am updating an object/document in OrientDB using a SQL statement but my connection is still returning the old version when I select it. It appears that the local cache does not know that the SQL updated that object.
Is there a way to flush that object from the cache of all the connections? Or should my code be updated/rewritten to use the direct document API to ensure concurrency? Turning the cache off solved this in the 1.7+ versions but this is causing me problems in 2.0 where I cannot turn the cache off. I am using OrientDB 2.0.5 -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
