Re: [Neo4j] Are Unique Indices in the Works?

James, Would a simple check in a new REST endpoint to the job or do you think this should be further down in the index configuration supporting unique properties and throwing an exception or silently update a property if a second insertion call comes? /Peter On Saturday, August 6, 2011, espeed

Re: [Neo4j] GSoC 2011 Neo4j Geoprocessing | Weekly Report #10

Good work Andreas ! Did you even update the Geoserver wiki page in order to be able to test it out? /peter On Saturday, August 6, 2011, Andreas Wilhelm a...@kabelbw.de wrote: Hi, This and the last week I debugged the GeoServer to find the problem why the integeration of the Neo4j Spatial

Re: [Neo4j] GSoC 2011 Neo4j Geoprocessing | Weekly Report #10

in process ;-) Am 06.08.2011 08:44, schrieb Peter Neubauer: Good work Andreas ! Did you even update the Geoserver wiki page in order to be able to test it out? /peter On Saturday, August 6, 2011, Andreas Wilhelma...@kabelbw.de wrote: Hi, This and the last week I debugged the GeoServer

Re: [Neo4j] Are Unique Indices in the Works?

What one could do at a lower level is to create operations like db.obtainUniqueNode(Map properties,String...idProperties); node.obtainUniqueRelationship(dir, type, props, String...idProperties); node.obtainUniqueRelationship(dir, type, targetNode, props, String...idProperties); which handle the

Re: [Neo4j] Keeping context information in the Graph

What you describe here is a ternary edge, something I try to cover in the Enhanced API. Your film example can be modeled as follows: There is an Edge STARS with the EdgeRoles: Actor, Film, Role. We can now state: STARS -- Actor -- Brad Pitt -- Film -- Fight club -- Role -- Tyler Durden

Re: [Neo4j] Are Unique Indices in the Works?

Michael Hunger wrote: What one could do at a lower level is to create operations like db.obtainUniqueNode(Map properties,String...idProperties); node.obtainUniqueRelationship(dir, type, props, String...idProperties); node.obtainUniqueRelationship(dir, type, targetNode, props,

Re: [Neo4j] Node#getRelationshipTypes

I would not consider this low hanging fruit btw Den onsdagen den 3:e augusti 2011 skrev Niels Hoogeveenpd_aficion...@hotmail.com: Hmmm... Does that require the inclusion of golden parachutes as well? Anyway, addressing the readers of this message that have time allocation authority. I hope

Re: [Neo4j] Node#getRelationshipTypes

Oh, confused this thread with store layer changes for type/direction of relationships. This fruit in this thread is pretty low hanging. Den lördagen den 6:e augusti 2011 skrev Mattias Perssonmatt...@neotechnology.com: I would not consider this low hanging fruit btw Den onsdagen den 3:e augusti

Re: [Neo4j] Node#getRelationshipTypes

This is the thread about store layer changes for type/direction, and in my opinion this is still quite low hanging fruit. Sure, the impact needs to be tested rigorously, which may take considerable time, but the implementation is quite straight-forward and the potential gains are large. Niels

Re: [Neo4j] Enhanced API rewrite

Today I added fluency to the API design. It is now possible to write: Db().createVertex() .setProperty(Name, John) .setProperty(Age, 29) .addEdgeTo(june, WIFE) I also added support for VertexTypes, which is nothing more and nothing less than a Vertex with a unique name and a class name to

Re: [Neo4j] Are Unique Indices in the Works?

Michael Hunger wrote: Probably we have to add this unique property behavior to the auto-indexing framework. Right now we have no means to mark properties as unique. So whenever you take a different node and set one of its unique properties to a value already contained in an unique