The problem is actually to do with how Javascript handles numeric values. It treats them as a double so hence if you have a big enough long you won't see the correct value displayed. I think it probably won't be properly fixed until we have a custom protocol interacting with the client rather than using JSON.
That's planned for one of the upcoming releases but I don't think it's been prioritised to a specific one yet. On 4 June 2014 09:07, Chris Skardon <[email protected]> wrote: > Hullo, > > This stems from: > http://stackoverflow.com/questions/24013425/asp-net-neo4jclient-retrieving-incorrect-number/ > Basically, a long is being stored in the DB (for > example: 635374684469251139) but gets rendered by the browser > as: 635374684469251200 > > To replicate: > > *Create Node:* > CREATE (n:Test {LongVal:635374684469251139}) > > *Return Node Value:* > MATCH n RETURN n.LongVal > > *Expect* > n.LongVal 635374684469251139 > > *Actual* > n.LongVal 635374684469251200 > > Data wise, the correct data is in the DB, running the same query through > the Console gives the right result (and via Neo4jClient), but obviously > when you look at the db in the browser the data *looks* different, hence > the question on SO. > > Cheers > > Chris > > -- > 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.
