Done. Thanks.
On Wed, Mar 26, 2014 at 9:21 AM, Michael Hunger < [email protected]> wrote: > Yep, right this rather looks like a bug. Can you raise it on GitHub? > Thanks a lot. > > > On Wed, Mar 26, 2014 at 1:49 PM, Javier de la Rosa <[email protected]>wrote: > >> Then, why not return a 404? That would be more consistent. >> >> >> On Wed, Mar 26, 2014 at 3:03 AM, Michael Hunger < >> [email protected]> wrote: >> >>> Hi Javier, >>> >>> Yes as the tx is not yet committed other tx don't see the node >>> >>> Only your ongoing tx request can access it >>> >>> Michael >>> >>> Sent from mobile device >>> >>> Am 26.03.2014 um 05:14 schrieb Javier de la Rosa <[email protected]>: >>> >>> Hello, >>> >>> I have a simple request that creates a transaction with a Cypher query >>> to create a node with label 'User' and a property 'name' with value 'Me': >>> >>> $ curl -X POST -d'{"statements":[{"statement":"CREATE (me:User {name: >>> \"Me\"}) RETURN me;", "resultDataContents": ["REST"]}]}' -H >>> accept:application/json -H content-type:application/json >>> http://localhost:7474/db/data/transaction/ >>> >>> The result of the query is as expected and the data for the new node >>> with id 147 is properly returned: >>> >>> { >>> "commit":"http://localhost:7474/db/data/transaction/88/commit";, >>> "results":[ >>> { >>> "columns":[ >>> "me" >>> ], >>> "data":[ >>> { >>> "rest":[ >>> { >>> "outgoing_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/out";, >>> "labels":" >>> http://localhost:7474/db/data/node/147/labels";, >>> "all_typed_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/all/{-list|&|types} >>> ", >>> "traverse":" >>> http://localhost:7474/db/data/node/147/traverse/{returnType}";, >>> "self":"http://localhost:7474/db/data/node/147";, >>> "property":" >>> http://localhost:7474/db/data/node/147/properties/{key}";, >>> "outgoing_typed_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/out/{-list|&|types} >>> ", >>> "properties":" >>> http://localhost:7474/db/data/node/147/properties";, >>> "incoming_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/in";, >>> "create_relationship":" >>> http://localhost:7474/db/data/node/147/relationships";, >>> "paged_traverse":" >>> http://localhost:7474/db/data/node/147/paged/traverse/{returnType}{?pageSize,leaseTime} >>> ", >>> "all_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/all";, >>> "incoming_typed_relationships":" >>> http://localhost:7474/db/data/node/147/relationships/in/{-list|&|types} >>> ", >>> * "data":{* >>> * "name":"Me"* >>> * }* >>> } >>> ] >>> } >>> ] >>> } >>> ], >>> "transaction":{ >>> "expires":"Wed, 26 Mar 2014 03:58:44 +0000" >>> }, >>> "errors":[] >>> } >>> >>> However, if during the time the transaction is open I try to fetch the >>> node by its REST URL, data always comes empty until the transaction is >>> committed. Is that the right behaviour? >>> >>> $ curl http://localhost:7474/db/data/node/147/ >>> { >>> "extensions" : { >>> }, >>> "outgoing_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/out";, >>> "labels" : "http://localhost:7474/db/data/node/147/labels";, >>> "all_typed_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/all/{-list|&|types} >>> ", >>> "traverse" : " >>> http://localhost:7474/db/data/node/147/traverse/{returnType}";, >>> "self" : "http://localhost:7474/db/data/node/147";, >>> "property" : "http://localhost:7474/db/data/node/147/properties/{key} >>> ", >>> "outgoing_typed_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/out/{-list|&|types} >>> ", >>> "properties" : "http://localhost:7474/db/data/node/147/properties";, >>> "incoming_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/in";, >>> "create_relationship" : " >>> http://localhost:7474/db/data/node/147/relationships";, >>> "paged_traverse" : " >>> http://localhost:7474/db/data/node/147/paged/traverse/{returnType}{?pageSize,leaseTime} >>> ", >>> "all_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/all";, >>> "incoming_typed_relationships" : " >>> http://localhost:7474/db/data/node/147/relationships/in/{-list|&|types} >>> ", >>> * "data" : {* >>> * }* >>> } >>> >>> Cheers! >>> >>> -- >>> Javier de la Rosa >>> http://versae.es >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Neo4j" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Neo4j" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Javier de la Rosa >> http://versae.es >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Neo4j" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Javier de la Rosa http://versae.es -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
