pg@9.0 breaking changes ideas #3598
Replies: 3 comments
-
remove queryQueueThe "query queue" idea shipped w/ the original version of node-postgres some 15 years ago. It gums up the internals of the client a bit, isn't how most database drivers behave, and is just weird. Espesh w/ async/await I don't think its used much at all on purpose. So, my plan is to deprecate it very soon in the pg@8.x branch - if someone adds a query to the client's internal query queue while the client is already executing a query in flight, I'll log a 1 time deprecation warning to the terminal. In 9.x the behavior will change to throw an error if a query is sent while another query is in flight. |
Beta Was this translation helpful? Give feedback.
-
update pg-typesBecause the version of pg-types I'm using is so many years behind the mainline branch I'm sure there are some breaking changes. I will not ever change the default "timezoneless date parsing" to be a different timezone, so either that needs to get reverted it pg-types 5.x or I'll have to patch over that part. Changing that would be a very subtle breaking change with no way to lint for it as it would be based on database types so I don't think its worth it...even though yeah if I had started out today I would try to align it w/ the way |
Beta Was this translation helpful? Give feedback.
-
pool.end() does not render the pool unusable afterward.2 things actually.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to gather feedback on breaking changes to make for pg@9.0. I'd like to start working on getting pg@9.0 out sometime in March so there's plenty of time for ideas!
Beta Was this translation helpful? Give feedback.
All reactions