Hi Jason, No limitation, but if you switch from a database to the other you could have problem. I suggest to always force the current database in ThreadLocal with:
ODatabaseThreadLocal.INSTANCE().set( db ); Where "db" is the db instance you want to use. Lvc@ On 24 June 2014 20:08, Jason Nichols <[email protected]> wrote: > Hi Guys, > Are there any restrictions or limitations on using multiple embedded > OObjectDatabaseTx within a single VM? I'm attempting to create multiple > OODB instances like such: > > odb = new OObjectDatabaseTx("plocal:" + dbPath); > > Where the dbPath can vary. I end up with multiple OODB instances, but > they each same to use the same local db folder, regardless of what path I > specify in the constructor. > > Thanks! > > -- > > --- > 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.
