HI, You should not do this. It would be very inconvenient, it is done automatically now. We had issue with DB life cycle management in previous pool implementation now it is fixed. I remember that we had similar kind of discussion with you in mailing list and I promised you that it will be fixed in 2.0 :-) .
On Sat, Jan 24, 2015 at 10:34 AM, odbuser <[email protected]> wrote: > Luca, the cache behavior still needs to be clarified in the > documentation. I've seen this question asked a few times but not fully > addressed unless I am missing something. > > In other words before every "request" in my app I have to do the following > to the open graph otherwise writing in a thread followed by a read from > another where that data was cached results in a dirty read: > > OrientGraph orientGraph = ... > ODatabaseDocumentTx rawGraph = orientGraph.getRawGraph(); > OLocalRecordCache localCache = rawGraph.getLocalCache(); > localCache.invalidate(); > > Is this what users are expected to do? If so, it's a major use case that > needs to be explicit in the documentation. > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. -- --- 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.
