I started using OrientDB because it is an "Object Database". I am not interreseted (yet) in a graph db or document db even if I am pleased to know I will always be able to use them if needed.
I use the Object Database Interface since version 0.9 (I am currently running v1.5.x on several project). I encountered a lot of bug since the begining, and as the version I use right now is running fine for me it's why I didn't upgrade (but I have plan to). Removing Object Interface is a _huge_ step back for me. And your workaround doesn't make sense for my project (really ... going through o2r mapping looks a better choice). Could you be really clear on the situation as I would be able to take decision for myself: spending time to upgrade my project to new OrientDB doesn't make sense if you (slowly) drop any support on Object Interface. Still, thanks for all your work done on OriendDB. One more though: Is there so much need for a Graph Database on the market instead of a real Object Database ? I still don't get how in 2014 we all use OO langage but no OO native persistence ! -- --- 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.
