{"action":"closed","issue":{"url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/245","repository_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver","labels_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/245/labels{/name}","comments_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/245/comments","events_url":"https://api.github.com/repos/neo4j/neo4j-javascript-driver/issues/245/events","html_url":"https://github.com/neo4j/neo4j-javascript-driver/issues/245","id":230458755,"number":245,"title":"Handling integers","user":{"login":"hierozbosch","id":4290207,"avatar_url":"https://avatars2.githubusercontent.com/u/4290207?v=4","gravatar_id":"","url":"https://api.github.com/users/hierozbosch","html_url":"https://github.com/hierozbosch","followers_url":"https://api.github.com/users/hierozbosch/followers","following_url":"https://api.github.com/users/hierozbosch/following{/other_user}","gists_url":"https://api.github.com/users/hierozbosch/gists{/gist_id}","starred_url":"https://api.github.com/users/hierozbosch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hierozbosch/subscriptions","organizations_url":"https://api.github.com/users/hierozbosch/orgs","repos_url":"https://api.github.com/users/hierozbosch/repos","events_url":"https://api.github.com/users/hierozbosch/events{/privacy}","received_events_url":"https://api.github.com/users/hierozbosch/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2017-05-22T16:59:32Z","updated_at":"2018-02-02T16:27:04Z","closed_at":"2018-02-02T16:27:04Z","author_association":"NONE","body":"The handling of integers is referenced in previous issues (153, 122, 106, etc.).  These issues have been closed and point to the Bolt driver methods (InSafeRange, int, etc.) as the resolution.  However, using these methods implies hard-coding conversions against a known set of data entities, and doing it on the server.  It's a highly inefficient solution:  the driver should only convert 64-bit numbers to {high: low:} objects as a last resort.  Converting all integers into these objects and then requiring a server to locate and re-convert most of them back into JS numbers is not an ideal solution.  I'm using the neo4j-javascript-driver for a web app, and I would be very surprised if serious 64-bit applications considered JS their language of choice.  In my case:  a.)  all my numbers are JS numbers, both in and out of neo4j;  b.) I do not want to use my back-end neo4j server and front-line web servers to convert JS integers into objects and then convert those objects back into JS integers; and c.) I do not want to hard-code my server or client scripts to the granularities of a data model.  I'm raising this as a new issue:  I think the neo4j-JS-driver should have an optional directive to convert 64-bit integers directly to JS numbers and not waste time converting them all into objects.  Thanks! "}}
{"actor":{"display_login":"lutovich"}}