thanks.. this solves many issues on our side
best,
Tom
Met vriendelijke groet / With kind regards
Ir. T. Zeppenfeldt
van der Waalsstraat 30
6706 JR Wageningen
The Netherlands
Mobile: +31 6 23 28 78 06
Phone: +31 3 17 84 22 17
E-mail: t.zeppenfe...@ophileon.com
<t.zeppenfe...@ophileon.com>Web: www.ophileon.com
Twitter: tomzeppenfeldt
Skype: tomzeppenfeldt
2015-05-14 1:12 GMT+02:00 Michael Hunger <michael.hun...@neotechnology.com>:
> you can simulate that by returning maps:
>
> RETURN {id:id(n), labels:labels(n), properties:n, metadata: "some-value"}
> as n
>
>
> Am 13.05.2015 um 11:14 schrieb Tom Zeppenfeldt <tomzeppenfe...@gmail.com>:
>
> We have a usecase in which styling of a node depends on the user and the
> (properties of a) relationship it has with other nodes. While trying to
> figure out how to do such a thing, we realized that it would be nice to
> have a possibility to "insert" properties in nodes or rels . Not SETting
> them and writing them to disk, but just inserting them in the result.
>
> MATCH (n)-[r]->(m)
> INSERT n.newproperty = r.someproperty, n.anotherproperty= m.xyz
> RETURN n LIMIT 1
>
> the result would be something like
>
> {
> "columns": ["n"],
> "data": [[{
> "outgoing_relationships": "
> http://localhost:7474/db/data/node/37/relationships/out";,
> "labels": "http://localhost:7474/db/data/node/37/labels";,
> "data": {},
> "all_typed_relationships": "
> http://localhost:7474/db/data/node/37/relationships/all/{-list|&|types}",
> "traverse": "
> http://localhost:7474/db/data/node/37/traverse/{returnType}";,
> "self": "http://localhost:7474/db/data/node/37";,
> "property": "
> http://localhost:7474/db/data/node/37/properties/{key}";,
> "properties": "http://localhost:7474/db/data/node/37/properties";,
> "outgoing_typed_relationships": "
> http://localhost:7474/db/data/node/37/relationships/out/{-list|&|types}",
> "incoming_relationships": "
> http://localhost:7474/db/data/node/37/relationships/in";,
> "extensions": {},
> "create_relationship": "
> http://localhost:7474/db/data/node/37/relationships";,
> "paged_traverse": "
> http://localhost:7474/db/data/node/37/paged/traverse/{returnType}{?pageSize,leaseTime}
> ",
> "all_relationships": "
> http://localhost:7474/db/data/node/37/relationships/all";,
> "incoming_typed_relationships": "
> http://localhost:7474/db/data/node/37/relationships/in/{-list|&|types}",
> "metadata": {
> "id": 37,
> "labels": ["somelabel"]
> },
> "inserted": {
> "newproperty": 1,
> "anotherproperty": "abc"
> }
> }]]
> }
>
> --
> 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 neo4j+unsubscr...@googlegroups.com.
> 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 neo4j+unsubscr...@googlegroups.com.
> 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 neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
