findings. Apart from traversals it is more or less
feature complete, but it could use some thorough trying out.
Niels
Date: Mon, 8 Aug 2011 20:20:14 +0500
From: shaban...@gmail.com
To: user@lists.neo4j.org
Subject: Re: [Neo4j] Enhanced API rewrite
I ready to jump in too ;-)
On Mon, Aug 8
...@neotechnology.com
Date: Mon, 8 Aug 2011 11:50:35 +0200
To: user@lists.neo4j.org
Subject: Re: [Neo4j] Enhanced API rewrite
Very interesting thoughts!
I would love to have a bootcamp and explore a spike on how this would
work out in practice. Got anything to do this autumn? ;)
Cheers,
/peter
I ready to jump in too ;-)
On Mon, Aug 8, 2011 at 3:37 PM, Niels Hoogeveen
pd_aficion...@hotmail.comwrote:
I can probably find the time for that. It would be fun working on these
ideas in collaboration. I don't mind producing my usual brain-dumps and
write some of the code, but quality will
To: user@lists.neo4j.org
Subject: Re: [Neo4j] Enhanced API rewrite
I ready to jump in too ;-)
On Mon, Aug 8, 2011 at 3:37 PM, Niels Hoogeveen
pd_aficion...@hotmail.comwrote:
I can probably find the time for that. It would be fun working on these
ideas in collaboration. I don't mind
Niels,
this sounds very interesting. Given the role of properties being unary
edges, that would mean that any classic Neo4j property would now be a
Node with one Property in the new Vertex sense?
Having Vertices for EVERYTHING will of course make the
node-implementation much more important than
easily be seen as a query language giving access to all parts
of the database.
Niels
From: peter.neuba...@neotechnology.com
Date: Sun, 7 Aug 2011 09:10:02 +0200
To: user@lists.neo4j.org
Subject: Re: [Neo4j] Enhanced API rewrite
Niels,
this sounds very interesting. Given the role
as EdgeType
(which extends VertexType) will be used for traversals.
Niels
From: pd_aficion...@hotmail.com
To: user@lists.neo4j.org
Date: Sat, 6 Aug 2011 02:51:23 +0200
Subject: [Neo4j] Enhanced API rewrite
Today I pushed a major rewrite of the Enhanced API. See:
https://github.com
Today I pushed a major rewrite of the Enhanced API. See:
https://github.com/peterneubauer/graph-collections/tree/master/src/main/java/org/neo4j/collections/graphdb
Originally the Enhanced API was a drop-in replacement of the standard Neo4j
API. This resulted in lots of wrapper classes that
On Sat, Aug 6, 2011 at 5:51 AM, Niels Hoogeveen
pd_aficion...@hotmail.comwrote:
...
Every part of the database can be accessed with a traveral description.
The standard Neo4j API only allows traversals to return Nodes given a start
Node. The Enhanced API allows traversals from any part
9 matches
Mail list logo
