Changelog History
Page 7
-
v3.1.0 Changes
April 09, 2020- 🐎 Switch internal protocol parser & serializer to pg-protocol. The change is backwards compatible but results in a significant performance improvement across the board, with some queries as much as 50% faster.
-
v3.0.8
May 08, 2020 -
v3.0.7
April 22, 2020 -
v3.0.6
April 09, 2020 -
v3.0.5
April 09, 2020 -
v3.0.4
March 30, 2020 -
v3.0.3
February 20, 2020 -
v3.0.2
January 30, 2020 -
v3.0.1
January 29, 2020 -
v3.0.0 Changes
January 10, 2020💥 Breaking changes
📚 After some discussion it was decided node-postgres was non-compliant in how it was handling DATE results. They were being converted to UTC, but the PostgreSQL documentation specifies they should be returned in the client timezone. This is a breaking change, and if you use the
datetype you might want to examine your code and make sure nothing is impacted.[email protected] included changes to not convert large integers into their JavaScript number representation because of possibility for numeric precision loss. The same types in arrays were not taken into account. This fix applies the same type of type-coercion rules to arrays of those types, so there will be no more possible numeric loss on an array of very large int8s for example. This is a breaking change because now a return type from a query of
int8[]will contain string representations 💅 of the integers. Use your favorite JavaScript bignum module to represent them without precision loss, or punch over the type converter to return the old style arrays again.Single
dateparameters were properly sent to the PostgreSQL server properly in local time, but an input array of dates was being changed into utc dates. This is a violation of what PostgreSQL expects. Small breaking change, but none-the-less something you should check out if you are inserting an array of dates.✅ This is a small change to bring the semantics of query more in line with other EventEmitters. The tests all passed after this change, but I suppose it could still be a breaking change in certain use cases. If you are doing clever things with the
endanderrorevents of a query object you might want to check to make sure its still behaving normally, though it is most likely not an issue.🆕 New features
The long & short of it is now any object you supply in the list of query values will be inspected for a
.toPostgresmethod. If the method is present it will be called and its result used as the raw text value sent to PostgreSQL for that value. This allows the same type of custom type coercion on query parameters as was previously afforded to query result values.🛠 If domains are active node-postgres will honor them and do everything it can to ensure all callbacks are properly fired in the active domain. If you have tried to use domains with node-postgres (or many other modules which pool long lived event emitters) you may have run into an issue where the active domain changes before and after a callback. This has been a longstanding footgun within node-postgres and I am happy to get it fixed.
Avoids a scenario where your pool could fill up with disconnected & unusable clients.
📚 To provide better documentation and a clearer explanation of how to override the query result parsing system we broke the type converters into their own module. There is still work around removing the 'global-ness' of the type converters so each query or connection can return types differently, but this is a good first step and allow a lot more obvious way to return int8 results as JavaScript numbers, for example