Date: Thu, 10 May 2012 07:23:40 -0700 (PDT)
From: kantube <mich...@mkanner.com>
To: neo4j@googlegroups.com
Message-ID: <23142577.711.1336659820960.JavaMail.geo-discussion-forums@yndm3>
In-Reply-To: <CAL4Xk+37qxwaJah9ghEvU-jf10N_H=iW4QhFxApxbD3Pbf2RQA@mail.gmail.com>
References: <5717923.1008.1336582988259.JavaMail.geo-discussion-forums@yndm3>
 <CAL4Xk+37qxwaJah9ghEvU-jf10N_H=iW4QhFxApxbD3Pbf2RQA@mail.gmail.com>
Subject: Re: [Neo4j] Batch and Unique Index over REST
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_709_13630291.1336659820960"

------=_Part_709_13630291.1336659820960
Content-Type: multipart/alternative; 
	boundary="----=_Part_710_8206810.1336659820960"

------=_Part_710_8206810.1336659820960
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Mattias,

thanks, with this call being "get or create" the response makes sense.  
however i don't think that this is the easiest of responses to work with.  
for example if you call this method with a mapping that already exists you 
get a node back that may not have the same properties as the node you 
passes in.  that is a bit confusing because you would think that the 
returned node would be the same as the one passed in.  This is different 
behavior from a RDBMS.  

However, would it be possible to add another method that would return 302 
(or some other non-2xx status code) if the node or relationship in 
questions already exists.  New methods with "?uniqueCreate" instead of 
"?unique" would be good enough.  this would function more like an RDBMS 
and, more importantly, would allow for batch processing of calls in a singe 
transaction over REST that require uniqueness, as state above.    

------=_Part_710_8206810.1336659820960
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Mattias,<br><br>thanks, with this call being "get or create" the response makes sense.&nbsp; however i don't think that this is the easiest of responses to work with.&nbsp; for example if you call this method with a mapping that already exists you get a node back that may not have the same properties as the node you passes in.&nbsp; that is a bit confusing because you would think that the returned node would be the same as the one passed in.&nbsp; This is different behavior from a RDBMS.&nbsp; <br><br>However, would it be possible to add another method that would return 302 (or some other non-2xx status code) if the node or relationship in questions already exists.&nbsp; New methods with "?uniqueCreate" instead of "?unique" would be good enough.&nbsp; this would function more like an RDBMS and, more importantly, would allow for batch processing of calls in a singe transaction over REST that require uniqueness, as state above. &nbsp;&nbsp; <br>
------=_Part_710_8206810.1336659820960--

------=_Part_709_13630291.1336659820960--