On 10/19/2016 03:38 PM, 'Nigel Small' via Neo4j wrote:
> Hi
>
> As Alan mentions, this is a side-effect of both Neo4j's type system
> and the JSON format used by the HTTP server. The type system at store
> level has no concept of an untyped array and JSON has no way to
> transmit type information i
Hi
As Alan mentions, this is a side-effect of both Neo4j's type system and the
JSON format used by the HTTP server. The type system at store level has no
concept of an untyped array and JSON has no way to transmit type
information independent of value, so it's impossible for the server to
determin
Maybe I'm missing something but why do you want to store an empty array as a
property? An empty array is logically equivalent to null. Null is logically
equivalent to not storing a value for hat property. Not storing a value for a
property is more efficient than writing value = null to disk.
S
In their data typing system, they need to know the type of the array
elements.
For example: Is it an array of strings, or ints, or floats?
There is no "array of to-be-determined"...
So, they don't consider it a bug...
In my case either I don't set that attribute to a value when I create
the obj
CREATE (root {name: "foobar", cars: []}) RETURN root
Queries, like above are impossible through rest
https://github.com/philippkueng/node-neo4j/issues/12
https://github.com/versae/neo4j-rest-client/issues/130
Isn't it a bug?
--
You received this message because you are subscribed to the Googl
