I've tried as many different permutations of the above as I can think of. - I trued to change the order of the 'attach' and and command creation; shuffling seems to have no effect (as expected). - I also tried nested transactions, which do seem like they're supported in some cases, but don't seem to work here. Again, tried many different permutations, but consistently seemed that the first 'commit' would close both transactions and exit the transaction context. Specifically, the second 'recordCreate' command, after closing the inner transaction, would result in a Record and not an Operation.
Happy to provide code on any of this if useful, though I'm hoping someone can just point out the right way. It boils down to: - start transaction - create record A - create B; reference A from B - commit Is this possible with OrientDB? Is it a limitation of the PHP client? This seems like a pretty common operation, but I'm unable to find any examples, which makes me wonder if I'm missing something. -- --- 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.
