Hi, this is a very good modelling question. Since xml has a tree structure it can be modeled with a graph without any problem (or mismatch).
Anyway as far as I know there isn't any API to work on orientdb as if it were an xml store, so you should map it by your own or, better, implement some known API using orientb as backend. First of all you should answer to some design question, for example: an xml child is a embedded document or a linked document? If you have more specific questions you could ask, otherwise it will be interesting to me if you find some geneal solution to this kind of problem. Cheers, Riccardo 2015-08-21 22:32 GMT+02:00 Sam <[email protected]>: > Hi there! > > OrientDB feature and support list is impressive. > > I wanted to check with community for view on using OrientDB purely to > store XML and to perform operations Insert, read, update and delete (CRUD) > search operations. > > Do you think using OrientDB will provide value in this context and shall > this usecase be implemented with OrientDB? > > Thank you! > Sam > > -- > > --- > 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.
