Hi guys, If you used OrientDB correctly, you will have no problem. If an *IllegalStateException* starts to be raised that's good news: your code used the same DB instance across threads with weird and unpredictable results.
Instead in case you manage multiple database from the same thread, you should activate the instance before using it. We could create a special wrapper that set itself as current for the case of multiple database management in one thread, but my fear is that everybody would use it with the same problems of past implementation. Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB <http://orientdb.com> On 11 June 2015 at 07:38, scott molinari <[email protected]> wrote: > Thanks Alex. > > Scott > > -- > > --- > 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. > -- --- 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.
