big integer array support
parse values in float arrays as floats not strings
Yes that is what it does. I agree too, it's a breaking change requiring a bump in the major. Just some more details:
Just as a note to myself - maybe I'll try to get a patch for this in before bumping the major version too?
@lalitkapoor thanks for this so much! 👍 sorry it took so long for me to merge it - needed to have some time & the mental fortitude to commit to doing a little refactoring in prep for email@example.com.
What's the recommended way to handle bigint postgres type?
Right now pg.defaults.parseInt8 is inconsistent:
CREATE TABLE testbigints(
a bigint DEFAULT array::bigint
When pg.defaults.parseInt8 = true:
Looks like both should be strings by default, and both should be numbers when pg.defaults.parseInt8 = true
pg.defaults.parseInt8 = true