If the data submitted exists purely in a single CompositeDescriptor, the "add" method of the GEOFFLoader class handles things in the correct order already.
Nige On 3 November 2011 18:22, Peter Neubauer <peter.neuba...@neotechnology.com>wrote: > Hi all, > following Nigels great work, I created a separate GEOFF plugin for the > Neo4j Server, https://github.com/neo4j/geoff-plugin (depending on > https://github.com/nigelsmall/neo4j-geoff-plugin, hoping to get both > building on CI soon) . It lets you submit GEOFF in JSON like > > POST http://localhost:7474/db/data/ext/GeoffPlugin/graphdb/insert > Accept: application/json > Content-Type: application/json > > {"geoff":{"(Joe)":{"name":"Joe"}}} > > Which results in the creation of a node with "name"="Joe". For more > cool examples, see http://py2neo.org/geoff/ > > Thanks a lot Nigel for pushing this! > > Now, I am not sure how to handle the ordering of things, like adding > indexes needs to be done after creating nodes, but it's a good start > :) > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > http://www.neo4j.org - NOSQL for the Enterprise. > http://startupbootcamp.org/ - Öresund - Innovation happens HERE. > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
