Hi, To add to the above question - what happens when multiple threads try to read the same data.
I was going through the documentation and noticed the following information - *LOCK* manage the locking strategy. By default is "default", that means release the lock once the record is read, while "record" means to keep the record locked in exclusive mode in current transaction till the transaction has been finished by a commit or rollback operation Source :https://github.com/orientechnologies/orientdb/wiki/SQL-Query Are the records locked for read? If yes, what is the recommended strategy to allow multiple threads to read the data. Is it optimistic locking? There are multiple business scenario in our application where we access the same record for read. Just to give some background we have migrated from RDBMS and in the new paradigm we were were wondering if it is a bad design to allow multiple threads to access the same record? Best Regards, Dobi On Thursday, January 15, 2015 at 1:42:29 PM UTC+5:30, Hung Tran wrote: > > Hi, > > At the moment, when a record is locked exclusively, other connections are > pending to read it. Is there a solution to work around of it? > > Any help would be greatly appreciated! > > My Best, > Hung Tran > -- --- 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.
