I have not come across many people who have used a Graph DB(such as a Neo4j) with Django. Even though there exist ORMs such as Neo4Django, I am not too happy with these solutions as they are potentially buggy and have very late development cycle. What do you suggests are best solutions?
-
what do you mean by late development cycle and "potentially buggy" ?Michael Hunger– Michael Hunger2014-05-20 12:34:35 +00:00Commented May 20, 2014 at 12:34
-
Buggy - github.com/scholrly/neo4django/issues?state=open there are many open fundamental issues and Late dev cycle because current solution is not compatible with neo4j 2.x and Django 1.6+ and there is no dev pipelineGaurav– Gaurav2014-05-20 15:29:28 +00:00Commented May 20, 2014 at 15:29
2 Answers
As of today, neo4django's latest commit is in July 2014. There seems to be bulbflow which mentions that it can be used from django. Its github link on their homepage is a broken URL. The only project I found linking bulbflow to django is https://github.com/theonion/django-bulbs , but it has a deprecation note to a broken URL. I just filed issue #338 requesting if they can provide a fixed link, and the developer clarified that it has been converted into a private repository.
This SO answer sheds some light and points mainly at py2neo. In the same SO question, there is another answer stating that django was designed with RDBMS in mind.
For alternatives to django as a web framework with neo4j as backend, this SO thread seems to be quite rich with options.
Funny enough, more search through duckduckgo.com led me to this blog post which is like a hello world example of using neo4j. It mentions neomodel (last commit 19 days ago), which links to django-neomodel (last commit 6 months ago).