Re: [Neo4j] py2neo - GEOFF enhancements

Having played around with some ASCII art (quite good fun actually!) it is starting to feel more natural to re-order the index entries, so that the key:value part is both consistent with existing syntax and adjacent to the index reference. I have ended up with: # ADD ENTRY: # ensure node "bert" has

Re: [Neo4j] py2neo - GEOFF enhancements

OK cool, that gives me some context. I'll put together some ideas over the next few days and we can compare notes :-) *Nigel Small* Phone: +44 7814 638 246 Blog: http://nigelsmall.name/ GTalk: ni...@nigelsmall.name MSN: nasm...@live.co.uk Skype: technige Twitter: @technige

Re: [Neo4j] py2neo - GEOFF enhancements

Peter and I have been discussing what interchange format we'd like to have for applications feeding data into a graph. And geoff seems to be quite a good choice. Modifying and accessing indexes (much like in-file-hooks) would be a part of that. So what I imagine is a set of connectors to outsi

Re: [Neo4j] py2neo - GEOFF enhancements

Hi Michael GEOFF was originally conceived as a graph serialisation format and, as such, was intended to represent a snapshot of entities at a particular point in time instead of, as you are discussing, a programmatic set of actions (add, replace, remove, etc). That said, these ideas are still wort

Re: [Neo4j] py2neo - GEOFF enhancements

Nigel, is it possible to also do index-lookups in geoff? and use those as nodes or rels or even as hooks for later on? I'm also toying with two other ideas: #1 using indexes as the third primitive besides nodes and rels in geoff just with a different delimeter (e.g. | as you already have) #2 gi

Re: [Neo4j] py2neo - GEOFF enhancements

Peter: I am happy with the current state of the neo4j-geoff code so feel it should be stable enough to adopt when you wish to do so. I have also made a couple of recent updates to the documentation, most notably the GEOFF.md file. Cheers Nige *Nigel Small* Phone: +44 7814 638 246 Blog: http://ni

Re: [Neo4j] py2neo - GEOFF enhancements

#1 Thanks #2 You're probably right #3 You can do the index lookup outside and pass in the IndexHits as being and Iterator #3 I rather thought of {name} for |people| -> {name: {hook}} as a shortcut for that Michael But #2 and #3 are probably overkill anyway. Cheers Michael Am 29.11.2011 um 2

Re: [Neo4j] py2neo - GEOFF enhancements

Hi Michael >Probably better to just return the full map and let the client code deal with it ? (If it isn't interested it would either just ignore the return result or discard it quickly). Done. Now works as: Map entities = GEOFFLoader.loadIntoNeo4j(reader, db, hooks); Node nodeFoo = (Node) entit

Re: [Neo4j] py2neo - GEOFF enhancements

Hmm good question, that means the namespace keeps everything around until it is gc'ed ? Probably better to just return the full map and let the client code deal with it ? (If it isn't interested it would either just ignore the return result or discard it quickly). Intention behind longs, is wh

Re: [Neo4j] py2neo - GEOFF enhancements

Hi Michael Doesn't handle iterables (yet) but should be quite easy to add in. What purpose did you have behind longs? I've just committed a few new methods allowing the Neo4jNamespace returned from a loadIntoNeo4j call to be used to retrieve new entities by name (or a map of such). The new method

Re: [Neo4j] py2neo - GEOFF enhancements

does it also handle iterables of nodes/rels (and probably Longs?) while thinking about it it would be great if the loader could also return a map of variables of the things generated to be used further in processing that could also interesting for cascading geoff and/or cypher cool stuff big t

Re: [Neo4j] py2neo - GEOFF enhancements

That sounds great! Let me know when you are stable, and I will see if I can do some more on the server plugin side, so we can shoot in things there! Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http://www.linkedin.com/in/neub

Re: [Neo4j] py2neo - GEOFF enhancements

Hi Peter Bulk of the work is now done on the Java version of the GEOFF enhancements. There have been some significant changes to the classes and a number of extra tests inserted. The signature of the load method has now been extended to: public static Neo4jNamespace loadIntoNeo4j(Reader reader, G

Re: [Neo4j] py2neo - GEOFF enhancements

Looks great to me Nigel! I think this is a very good first step on parameters. Let me know when you are done with the Java code, would like to bring this into the @Graph annotations after our next milestone release, 1.6.M01. /peter On Tue, Nov 22, 2011 at 10:14 PM, Nigel Small wrote: > Hi all >

[Neo4j] py2neo - GEOFF enhancements

Hi all I have just completed a set of GEOFF enhancements within py2neo (as yet only available from GitHub). Named parameters (hooks) and composite descriptors are now supported, please see the following sample file for an illustration of the new capabilites: https://github.com/nigelsmall/py2neo/b