Héllo, Sorry to shim in a probably a bit off and old topic discussion, I think we need to have this discussion, even if this is similar to any other nosql discussion, there is nothing really specific to OrientDB or any graphdb (Neo4J, Rexster server, ...).
I have no particular experience with OrientDB dev, as I'm more interested in Rexster server, but I hope I can be of some help. There is another old topic in django-users so you might want to check it too: - https://groups.google.com/d/topic/django-users/WHEmlrTVgWc/discussion I am planning to use orientDb with Django application (i am yet in design > stage). > Join the fun :) > I am not sure if i should just use simiple pyorient like library to access > orientDB or should i write new db driver etc > I don't think Django ORM can address the GraphDB issues just like it couldn't address mongodb things and that was the purpose of specific software Django-nonrel <https://github.com/django-nonrel/django-nonrel>(which looks unmaintened). Django-nonrel won't probably address it too, that said I never used django-nonrel, so I'm no best to give a definitive answer about the subject. > Basically my question is should i worry about not using django db > functionality if i write custom classes to represent model classes. > The question is vague. Are you aiming at using both a relationnal database and a graphdb or just a graphdb ? - Both: Since you can't use django orm with orientdb, you need to make the graphdb orm or deal in your code with the connection, querying to the graphdb - GraphDB only: the above solve this case. For other probable questions: - Can I create a graphdb (Neo4j, OrientDB, Rexster) driver for Django ORM, yes and no. It might be possible to get some of the functionnality of Django ORM working (crud, related object querying, filtering) but the ORM won't address features specific to the graphdbs which might make such a project useless. That's why I think people started their own ORM and there is no drivers for graphdb in relational orms I know of. - GraphDB + Django Admin ? No, there is yet no admin that can explore/edit a graphdb in Django even if such a thing might be possible to do. Django admin is bound to Django ORM, so this is not gonna happen in the forseable future unless there is a new admin that is decoupled from the Django ORM. Since I'm working on a new admin, I dig this issue but it's not a priority. - Is it possible to use a graphdb with Django ? Yes see the topic on django-users. Graph databases are a wonderful thing, I think more people should use them for the web and not only to solve specific problems related to graphs but also for generic web development. There is no or little done in this regard in the Python framework space because graphdbs are still, even if lately buzzing, in its infantility, but it can be of great help to rapidly prototype apps. What Django can do ? Nothing or little, like I said earlier even if graphdbs share some common patterns with relationnal databases I don't see the ORM evolve to support both kind of databases without putting dangerous tools in the hand of non-vigilant developpers. Cheers, Amirouche -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/kqSmKNCTTlQJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
