Skip to content
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

pg is outdated #143

Open
johanneskares opened this issue Feb 11, 2025 · 3 comments
Open

pg is outdated #143

johanneskares opened this issue Feb 11, 2025 · 3 comments

Comments

@johanneskares
Copy link

Node Postgres version is quite outdated form more than 2 years ago:

"pg": "8.8.0",

@jawj
Copy link
Collaborator

jawj commented Feb 11, 2025

That's true, and it's been on my hypothetical TODO list for a while to update. But it's not trivial, because we shim quite a few internals in a way that I know will need to change.

Are there any particular features or fixes you need that the latest version has?

@andyjy
Copy link
Contributor

andyjy commented Feb 11, 2025

I just came to request bump to the latest pg release v8.13.2 from today which includes fix for brianc/node-postgres#3373 ("Cannot set property message of #<_ErrorEvent> which has only a getter" on connection timeout).

Didn't realise it would be more of a major change to update but understand the situation. I'm currently applying this to the bundled pg via a patch so purely noting here in case it helps anyone else - I'm not blocked.

@johanneskares
Copy link
Author

Currently, with this old version, timestamps are returned as strings while date's are returned as JS Dates. I believe this default behavior was changed in a more recent version of pg and tools like kysely typegen expect both to be returned as Dates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants