-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
double precision field not parsed correctly, loss of precision #64
Comments
In case that helps, using pg-native returns the same truncated data :
|
And I have a workaround : it does not work correctly with double precision type, but it's ok with Numeric type and using setTypeParser. |
You’ll need to set |
I got similar issues. |
I get data from fields in postgresql 9.4 :
And setting up node-pg like this :
Data from pg looks like this :
But I get this with node-pg, whatever I do (default type parser, or with above override).
The result from node-pg :
I've read countless bug report and node-pg docs on this, seams like it should work correctly. Is this a bug ? Or something I'm not doing correctly ?
The text was updated successfully, but these errors were encountered: