Hi all, If anyone is interested, here is a small maven project which replicates the issue with some variations (AutostartTx, same or different value is written to the record...): https://github.com/emmedemme/OrientDBTests.git
To run the tests, from the root directory of the project: mvn [clean] [-U] test -Dtest=OrientTests* Thank you in advance! On Wednesday, October 22, 2014 11:48:40 AM UTC+2, Emanuele Milani wrote: > > Hi Andrey, > > I tried the same code with 2.0-SNAPSHOT (build 363), but unfortunetely the > problem is still there. Could you also replicate it? > I also tried to check if my local cache is enabled, but I only found in > the docs that it should be enabled by default. > I am now adding a small maven project on github, which just contains 3 > junit tests replicating the issue, and I will post the link as soon as I > push it. > > As "side" questions: > - is it safe to use (read from and write to) the same Vertex object across > multiple transactions? > - is it safe to expect that if a property is updated through a Vertex > object, all other Vertex objects referring to the same record will be aware > of the new values? > In both cases I am assuming a single threaded application, using one > OrientGraph object. > -- --- 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.
