@brianc I was talking about that earlier so that people would not try to
use the value as a raw string by accident.

On Fri, Mar 29, 2013 at 6:32 PM, Brian C notifications@github.com wrote:

That is an interesting and cool idea. You're saying basically wrap the
string result of a number in a class that does nothing but hold the string
so one could use 'instanceof' instead of just having to "know" a particular
column is a number?

The only counter I have to that is you could easily make that an add-on
module and snap it in to the type system instead of it being included with
node-Postgres itself. Something like 'require("pg-big-number")'

Long term I am trying to make node-postgres less opinionated and push more
features into other modules to be more "node-like"

Right now it suffers from being older than the idea of "do one tiny thing
in each node module" itself.

On Mar 29, 2013, at 4:53 PM, Ryan Pedela notifications@github.com
wrote:

What about wrapping it with a BigNumber class for int64 and numeric? The
class simply stores a string version of the number. But it is easier to
test if the object is a BigNumber such as:

if (num instanceof BigNumber) {
// use your favorite big number arithmetic library
}
I did this for a custom JSON parser since we needed to support large
numbers on our server. You can find the custom JSON parser here:
https://github.com/datalanche/json-bignum

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/266#issuecomment-15663790
.

Uh oh!

parseFloat not good for type conversion #266

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions