We also have some locking issues in our application. We couldn't figure out the causes from the error message. It would be nice if the OritentDB team can provide detailed documentation ( in both SQL and Document API level)about the locking strategy, and what are the recommended implementations for concurrent reading and/or writing. I think it is a critical piece of information for developers who use OrientDB in a server application.
Thanks, Jing > > > > > 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
