Re: [Neo4j] REST put over writing old properties

2010-08-23 Thread Mattias Persson
Hi Suhail, this is expected behaviour. PUT semantics in general means replace any existing data with the data I'm sending over right now. So if you'd like to add/set a property foo (and only foo) please use: PUT /node/123/properties/foo with bar as the payload/entity 2010/8/23, Suhail Ahmed

Re: [Neo4j] REST put over writing old properties

2010-08-23 Thread Suhail Ahmed
Thank Mattias. On Mon, Aug 23, 2010 at 7:31 AM, Mattias Persson matt...@neotechnology.comwrote: Hi Suhail, this is expected behaviour. PUT semantics in general means replace any existing data with the data I'm sending over right now. So if you'd like to add/set a property foo (and only foo)

[Neo4j] REST put over writing old properties

2010-08-22 Thread Suhail Ahmed
Hi, i have been trying out the Neo4j REST interface and I found that PUT operation was replacing the existing properties of a node with a new one. This was happening on single values as well as multiple values. Is this a bug or am I doing something wrong here. I am using the REST plugin with

Re: [Neo4j] REST put over writing old properties

2010-08-22 Thread David Montag
Hi Suhail, Could you explain the REST operation you're doing, what results you would expect from that operation, and what actually happens? David On Sun, Aug 22, 2010 at 9:11 AM, Suhail Ahmed suhail...@gmail.com wrote: Hi, i have been trying out the Neo4j REST interface and I found that PUT