Hi Dmitry, You can operate with all the API, respecting the constraints. For example if you've vertices and edges, you should create POJO that respect such inheritance and behavior. Usually Graph-Document is ok, the Object Database could be harder to let it working against a Graph model, but seems somebody did it.
Lvc@ On 9 July 2014 22:55, Dmitry <[email protected]> wrote: > > Hi! > > This question has been raised, but I would like to update the status. > Is it possible to use the same database in different modes (Document, > Object, Graph)? > > For example: > First module/application will through the Object Database API. > Second module will work through the Graph API and and will add edges > between entities. > Third module will work through Document API. > > Are drawbacks or potential problems with this approach? > Such performance problems for modules 1 (Object API) and / or 3 (Document > API). > > Thanks. > > -- > > --- > 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.
