Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The World's Most Amazing Python Driver for Neo4j

DZone's Guide to

The World's Most Amazing Python Driver for Neo4j

Here's a look at what py2neo can do for you when working with Neo4j.

· Database Zone
Free Resource

Whether you work in SQL Server Management Studio or Visual Studio, Redgate tools integrate with your existing infrastructure, enabling you to align DevOps for your applications with DevOps for your SQL Server databases. Discover true Database DevOps, brought to you in partnership with Redgate.

Learn about py2neo 3.1, a community Python driver for Neo4j, including the new Object-Graph Mapper

Even though we've now released officially supported drivers for Java, Python, JavaScript and .NET, many of the community drivers are still going strong. Indeed, version 3.1 of my own community driver py2neo was released this week and with it came a brand-new OGM for Python users.

An OGM (Object-Graph Mapper) is to a graph database what an Object-Relational Mapper (ORM) is to a traditional RDBMS: a framework on which database-aware domain objects can be built.

The py2neo OGM centers its operation around the new GraphObject class. This acts as both a base class upon which domain objects can be defined and a manager for the underlying node and relationships that persist it.

Take for example the Movie Graph that comes pre-packaged with Neo4j. We could model a Person from this dataset as below:

class Person(GraphObject):
    __primarykey__ = "name"

    name = Property()
    born = Property()


Here, we define a Person class with two properties. Properties in Neo4j have no fixed type, so there's less to define than there would be for a SQL field in a typical ORM. 

We're also using the same names for the class attributes as we do for the underlying properties: name and born. If necessary, these could be redirected to a differently named property with an expression such as Property(name="actual_name").

Lastly, we define a __primarykey__. This tells py2neo which property should be treated as a unique identifier for push and pull operations. We could also define a __primarylabel__ although by default, the class name Person will be used instead.

All of this means that behind the scenes, the node for a specific Person object could be selected using a Cypher statement such as:

MATCH (a:Person) WHERE a.name = {n} RETURN a

Broadening out a little, if we wanted to model both Person and Movie from that same dataset, as well as the relationships that connect them, we could use the following: 
class Movie(GraphObject):
    __primarykey__ = "title"

    title = Property()
    tagline = Property()
    released = Property()

    actors = RelatedFrom("Person", "ACTED_IN")
    directors = RelatedFrom("Person", "DIRECTED")
    producers = RelatedFrom("Person", "PRODUCED")

class Person(GraphObject):
    __primarykey__ = "name"

    name = Property()
    born = Property()

    acted_in = RelatedTo(Movie)
    directed = RelatedTo(Movie)
    produced = RelatedTo(Movie)

This introduces two new attribute types: RelatedTo and RelatedFrom. These define sets of related objects that are all connected in a similar way. That is, they share a common start or end node plus a common relationship type. 

Take for example acted_in = RelatedTo(Movie). This describes a set of related Movie nodes that are all connected by an outgoing ACTED_IN relationship. Note that like the property name above, the relationship type defaults to match the attribute name itself, albeit upper-cased. Conversely, the corresponding reverse definition, actors = RelatedFrom("Person", "ACTED_IN"), specifies the relationship name explicitly as this differs from the attribute name.

So how do we work with these objects? Let's say that we want to pluck Keanu Reeves from the database and link him to the timeless epic Bill & Ted's Excellent Adventure (sadly omitted from the original graph). First, we need to select the actor using the GraphObject class method select via the Person subclass. Then, we can build a new Movie object, add this to the set of movies acted_in by the talented Mr. Reeves and finally push everything back into the graph. The code looks something like this:

keanu = Person.select(graph, "Keanu Reeves").first()
bill_and_ted = Movie()
bill_and_ted.title = "Bill & Ted's Excellent Adventure"
keanu.acted_in.add(bill_and_ted)
graph.push(keanu)

All related objects become available to instances of their parent class through a set-like interface, which offers methods such as add and remove. When these details are pushed back into the graph, the OGM framework automatically builds and runs all the necessary Cypher to make this happen. 

More complex selections are possible through the select method as well. The where method can make use of any expression that can be used in a Cypher WHERE clause. For example, to output the names of every actor whose name starts with ‘K’, you could use:

for person in Person.select(graph).where("_.name =~ 'K.*'"):
    print(person.name)

Note that the underscore character is used here to refer to the node or nodes being matched.

There's a lot more information available in the py2neo documentation and there's also a demo application in the GitHub repository that shows how this all comes together in a mini movie browser (screenshot below).

The sample movie web app that comes with py2neo 3.1

As always, if you have any questions about py2neo or the official drivers, I’ll try my best to help. 

It’s easier than you think to extend DevOps practices to SQL Server with Redgate tools. Discover how to introduce true Database DevOps, brought to you in partnership with Redgate

Topics:
py2neo ,driver ,drivers ,properties ,python

Published at DZone with permission of Nigel Small, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}