He guys, We ty to use OrientDB 1.7 with the plocal mode in a frontend-application. In our application we would like to use the objectdatabase to persist our entities. One function in the programm should allow the user to save relationships between persons. So you see where this is going :)
Our first thought was to use the GraphDatabase to persist these relationships, so we tried to use object and graph at the same time. We defined the class customer in orientdb and set Vertex as superclass. This made it possible to use our entitie customer in graph operations and to store relationships. Unfortunaly this changes are obviously not transparent to the objectdatabase conncetion, which has now other versionIds for the customers with new relationships and blocks all new changes, if there was no refresh. So my queytion is: Are there any usefull known patterns for parallel use of this different connections? At the moment we tried to improve our orientdb-knowledge by using only one single documentconnection to create a graphconnection and the objectmapperlayer. The created behaviour is very close to our goals, but to reach it, we had to add a new constructor to the ObjectDatabaseTx.class, to bypass our documentconnection. I think there is a reason why this is not possible by default, so does anybody have some experience with this kind of usecase or knows some similarly post ? Thanks for your help or opinion Julian -- --- 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.
