Hi Josè, I'm not sure where the problem exactly is, but I can give you two pointers: 1) schema creation has to be managed outside of transaction, using OrientGraphNoTx 2) when you try to create an edge or a vertex, the driver checks whether the edge/vertex class exists, and in case it tries to create it
My general suggestion is to check/create the schema when the plugin starts up, using an OrientGraphNoTx Thanks Luigi 2015-07-13 20:30 GMT+02:00 José Cornado <[email protected]>: > Forgot to mention that I am running .12 on OSX 10.9 1.7 jvm. And creating > the instance as follows: > > OrientGraph("plocal:....") > > On Monday, July 13, 2015 at 9:54:18 AM UTC-6, José Cornado wrote: >> >> First, great job! I am embedding the graph DB inside an eclipse plug-in >> and the startup and shutdown are really fast. It is hard to notice that in >> addition to the plugin a DB is being used. >> >> Even when I do something wrong it fails quickly and gracefully. >> >> I have a question: >> >> As a rule of thumb I issue a begin/commit or rollback (commit if a write >> occurs rollback if it is only reading) every time I access the graph. Two >> threads access the graph: the ui thread and the backgrounder. Even though >> when the exception occurs the ui thread is idle. >> >> The message is kind of puzzling. What I am missing? >> >> Thanks a lot!! >> >> >> >> >> -- > > --- > 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.
