This sounds like a very nice project. I've wanted to do such a project myself but I've been kept back by lack of time.
I am a committer on the Jython project, and focus mainly on the compiler. About a year and a half ago I started a project for giving Neo4j a more Pythonic feel when used from Jython (and CPython), it is in the Neo4j repository as neo4j.py: https://svn.neo4j.org/components/neo4j.py/trunk/This could be a place for you to start on your Neo4j/Django project. At the moment I an busy working on a project I call RemoteNeo, it's an implementation of the Neo4j API that allows you to connect multiple clients to one server. But I hope to put some effort into neo4j.py soon as well (blog post with road map coming Monday or Tuesday). One thing I would like to incorporate is support libraries for using Neo4j with Django, so please submit feedback on places where the current neo4j.py feels awkward and extensions needed to use Neo4j in Django. Also let me know if I can be of assistance in any way. A quick feature list of features that neo4j.py enable (from the top of my head): * Access properties as: node_or_relationship["property key"] * Nodes and relationships supports most methods that dict supports. * Access relationships as: node.RELATIONSHIP_TYPE * Create: node1.Related_To(node2) * Iterate: for rel in node1.Related_To: ... * Use with-statement for transactions: with neo.transaction: ... * Exception in the with-suite will cause rollback Traversals are not that pretty yet, but they are supported, I would love input on how you'd like to define traversals in Python code. Cheers, Tobias On Fri, Nov 28, 2008 at 10:53 PM, James Richards <[EMAIL PROTECTED]> wrote: > I've been looking into using Neo4J inside of Django on Jython > > http://docs.djangoproject.com/en/dev/howto/jython/#howto-jython > > for similar reasons. It's ideal to me as it couples dynamic jython > with a stable rapid dev environment. Worth looking into if you want > to stick with python syntax. > > Regards, > > James > > > Hi all, > > > > I had an email exchange with Emil this morning about what Groovy could > > bring to using Neo4J. I think using a dynamic language with a graph > > database can make a lot of sense, as it's easier to work with a "less > > strict" language with semi structured data not requiring heavyweight > > set-in-stone schemas. > > > > Emil suggested I reproduce the email on this mailing-list, so I'm > > happy to echo my small brainstorming session below. > > > > I haven't used Neo4J so far, so I just based my ideas on the > > information I gathered looking at the quick start tutorial, so bare > > with me if I'm totally nuts ;-) > > > > Guillaume > > > > > > ---------------%<-------------------------------------- > > > > Hi Emil, > > > > First, a small introduction: I'm the project lead of the Groovy > > dynamic language. > > I've stumbled upon your presentation of Neo at QCon, on slideshare, > > and saw the mention of Groovy near the end :-) > > I've always been interested in triplestores, object databases, and so > > on, and thought that the flexibility they offer is something I really > > miss in relational databases. > > I'd love to use something like JCR, triplestores, or now Neo! for a > > pet project I had a while ago. > > I wish I had been at QCon this year, I would have loved to attend your > > session, but that was not the case. > > > > I haven't downloaded and tried Neo yet, but if I find some time, I'd > > be happy to give it a try. > > As you were mentioning that Groovy should probably work well with Neo, > > yes, I'm pretty certain it does, and I'm sure we could bring some > > Groovyisms into the loop to make using Neo even more seamless and > > nice. > > > > For instance, if I look at your quick start example: > > > > Node firstNode = neo.createNode(); > > Node secondNode = neo.createNode(); > > Relationship relationship = firstNode.createRelationshipTo( > > secondNode, MyRelationshipTypes.KNOWS ); > > > > firstNode.setProperty( "message", "Hello, " ); > > secondNode.setProperty( "message", "world!" ); > > relationship.setProperty( "message", "brave Neo " ); > > > > Groovy handles the setProperty/getProperty methods in a particular > > fashion, and without doing anything special, you should be able to > > directly use this nicer syntax in Groovy: > > > > firstNode.message = "Hello" > > secondNode.message = "world!" > > relationship.message = "brave Neo" > > > > It really gives people the impression of working with real objects, > > with real properties or methods. > > > > With maps or expandos in Groovy, you can already manipulate > > quasi-beans with that syntax, and people may potentially not need to > > manipulate Node or Relationship directly, but could use these maps / > > expandos instead, and it would only be when storing these in the graph > > database that you could "coerce" the type to Node or Relationship. > > > > More concretely: > > > > def firstNode = [:] > > firstNode.message = "Hello" > > > > And you could then just call some store() method in your APIs -- > > although it seems in the tutorial, there's no need to "store", just > > creating the nodes and relationships are enough. > > > > Also for relationships, we could imagine using Groovy's native list > > syntax for representing such triples (and using static import for > > KNOWS): > > > > def relationship = [ firstNode, KNOWS, secondNode ] > > > > Combining everything: > > > > [ > > [name: "Neo"], > > [KNOWS: [since: someDate], > > [name: "Trinity"] > > ] > > > > I was also mentioning coercion, as you can create custom type coercion > > in Groovy (kind of a cast, if you wish, but you can transform > > something into some other type): > > > > [name: "Neo"] as Node > > [ firstNode, KNOWS, secondNode ] as Relationship > > > > Or simply at declaration time: > > > > Node neo = [name: "Neo"] > > Relationship rel = [ firstNode, KNOWS, secondNode ] > > > > Anyway... enough brainstorming for now, but a graph database like Neo > > and a dynamic language like Groovy, and you can really really have > > fun. > > Congratulations for a great graph database project! > > Keep up the good work. > > > > -- > > Guillaume Laforge > > Groovy Project Manager > > Head of Groovy Development at SpringSource > > http://www.springsource.com/g2one > > _______________________________________________ > > Neo mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Tobias Ivarsson <[EMAIL PROTECTED]> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
