-
Notifications
You must be signed in to change notification settings - Fork 76
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
Get off of slonik fork #1119
Comments
Great to have these notes centralized here! Here are a few from me:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are currently using a fork of
slonik
: alxndrsn/slonik@b0299faThis is because of some stream-related issues.
At least one related patch has been accepted to upstream
node-postgres
: brianc/node-postgres#2836History of postgres clients used in Central:
postgres.js
A barrier to upgrading
slonik
has been several breaking changes since the version we were on. It seems there's likely a more deliberate approach to breaking changes now: gajus/slonik#450 (comment)There is now a bridge to use slonik on top of
postgres.js
instead ofnode-postgres
: https://github.com/gajus/postgres-bridgeThe text was updated successfully, but these errors were encountered: