Hi Peter Thanks Nigel for working hard on Py2neo - it's becoming a very cool binding! Thanks - I'm certainly pleased with how py2neo is turning out :-)
Thinking about your use cases in turn: - insert data as part of a JSON payload to existing nodes, encoded in GEOFF (kind of document substructures) - something like http://docs.neo4j.org/chunked/snapshot/rest-api-node-properties.html#rest-api-set-property-on-node but with a GEOFF payload that is resulting in a new subgraph We could possibly create some form of syntax which would designate a "this" node, e.g. (@). This could allow a file to reference it's external context, in this case the node to which we are submitting the subgraph. - insert a subgraph, but as part of the insertion, attach the subgraph to an existing stucture To reference the destination graph from within GEOFF would require either IDs or search criteria which could provide zero or more nodes as a result. I can see pros and cons for both approaches. On the other hand, we could look at the previous use case and consider some form of parameterised load routine. We could then possibly extend the syntax above to (@0) (@1) (@2) and so on to reference the passed-in nodes. - have PQL support mutating statements (INSERT, UPDATE etc) and maybe use GEOFF to describe substructures for mutations. I haven't looked at PQL yet but I'm guessing a similar syntax could be used to reference nodes within those statements. I'll look into it a bit more! Cheers * * *Nigel Small* Phone: +44 7814 638 246 Blog: http://nigelsmall.name/ GTalk: ni...@nigelsmall.name MSN: nasm...@live.co.uk Skype: technige Twitter: @technige <https://twitter.com/#!/technige> LinkedIn: http://uk.linkedin.com/in/nigelsmall On 10 November 2011 04:10, Peter Neubauer <peter.neuba...@neotechnology.com>wrote: > Thanks Nigel for working hard on Py2neo - it's becoming a very cool > binding! > > Also, GEOFF for the clean insertion of data is starting to shape up - > I am hoping to get server side support in after the release :) Related > to this is another issue. How are we going to insert subgraphs that > refer to existing nodes? There are a number of interesting scenarios > here: > > - insert data as part of a JSON payload to existing nodes, encoded in > GEOFF (kind of document substructures) - something like > > http://docs.neo4j.org/chunked/snapshot/rest-api-node-properties.html#rest-api-set-property-on-node > but with a GEOFF payload that is resulting in a new subgraph > > - insert a subgraph, but as part of the insertion, attach the subgraph > to an existing stucture > > - have PQL support mutating statements (INSERT, UPDATE etc) and maybe > use GEOFF to describe substructures for mutations. > > Any thoughts? > > 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. > > > > On Tue, Nov 8, 2011 at 9:02 AM, Nigel Small <ni...@nigelsmall.name> wrote: > > Hi all > > > > Have just released a small but hopefully significant (performance-wise) > > upgrade to py2neo: a rewrite to geoff.py which submits the entire set of > > data in a single self-referential batch. Available from GitHub and PyPI. > > > > Cheers > > * > > * > > *Nigel Small* > > Phone: +44 7814 638 246 > > Blog: http://nigelsmall.name/ > > GTalk: ni...@nigelsmall.name > > MSN: nasm...@live.co.uk > > Skype: technige > > Twitter: @technige <https://twitter.com/#!/technige> > > LinkedIn: http://uk.linkedin.com/in/nigelsmall > > _______________________________________________ > > 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 > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
