Hi all, I am trying to port Bitsy graph DB from TP2 to TP3. I have a few questions on TP3:
1. Is this mailing list searchable? I don't want to ask questions that have already been answered. 2. Is there any implementation that was ported from TP2 to TP3? I see many total rewrites, but I'm looking to see diffs across classes. 2b. Is there any example of an app that was ported from TP2 to TP3? If this process is hard, I'm thinking of launching the TP3 port as a separate project. 3. What happened to KeyIndexableGraph? We used to rely on this interface to find vertices by a natural key besides the UUID. 4. Should the tx() method always return the same object within the same thread, or a different object for each transaction? For instance: Transaction tx1 = g.tx(); tx1.open(); // .. do some stuff tx1.close(); assert tx1.isOpen() == false; Transaction tx2 = g.tx(); tx2.open(); At this point, if tx1 and tx2 are different objects, tx1.open() will launch two parallel transactions in the same thread. This means that two transactions can happen on the same thread. Is that allowed? If tx1 and tx2 are the same object, tx1.isOpen() will return true even though the transaction has been closed. (b) If tx1 or tx2 is accessed by a different thread, what is the accepted behavior? (c) I read somewhere (can't find it anymore) that transactions can be automatically opened when operations are performed. If so, how does the user know if the transaction is open or not? In other words, g.tx() will have to return the same object in the same thread for the user to be able to detect that a transaction is underway, if automatic open/close of transactions is allowed. Regards, Sridhar.
