Hi Steve, Can you provide a test case that prove this issue? We have plenty of test case on that. Probably you're executing an inner transaction, so it's never committed until the top level transaction is committed? Please double check it.
Lvc@ On 8 March 2015 at 13:59, Steve Hu <[email protected]> wrote: > This is what I did in 2.0.4 and it doesn't work. The schema types created > in notx won't be visible for tx graph to add vertex and Orientdb just hang. > Once restart the db server, the tx transaction is not committed. I think it > works if you wait for a while after notx then run the tx but it is hard to > identify how long. Should I use tx for both and ignore the warnings? > > > On Tuesday, March 25, 2014 at 11:56:07 AM UTC-4, odbuser wrote: >> >> pre-1.7rc2 (and maybe 1.7rc1 I'm not sure) >> OrientGraphBase graphNoTx = new OrientGraphNoTx(url); >> OrientGraphBase graphTx = new OrientGraph(url); >> >> post-1.7rc2 >> OrientGraphFactory factory = new OrientGraphFactory(url, user, password) >> OrientGraphBase graphNoTx = factory.getNoTx(); >> OrientGraphBase graphTx = factory.get(); >> >> Do your schema changes first using the NoTx graph. After that, just use >> the transactional graph as usual. You may have cases where you are making >> a decision about making schema changes during a transaction. If that's the >> case, you should re-organize the code so that you can make those decisions >> outside of the transaction (or apply them outside of the transaction). >> > -- > > --- > 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.
