-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Postgresql fails due to use of utf8mb4
default encoding
#153
Comments
Hi @Ramblurr Good catch! The default only works for mySQL but I think that the encoding should be passed in the connection string every time, so we might want to remove it altogether so the error message is clearer I'll do that soon |
It's interesting because the I suppose under the hood doctrine is parsing the URI and rebuilding it? |
Done in 7b50e1b — can you confirm it fixes your error? |
Thanks for the quick turnaround, I'll test this today. |
Is it all good on your side @Ramblurr? I'll probably release in the weekend Thanks! |
Gentle ping @Ramblurr on this one 🙏🏼 thanks |
Can confirm postgresql is working without manually setting |
* Our patchset is no longer required (see tchapi/davis#156) * Though the upstream var names changed, so we had to update those too * These vars are managed by the nixos module and hence are not breaking changes for users of the module. * Also removed need to specify postgres charset in non-standard way (see tchapi/davis#153) Release notes: https://github.com/tchapi/davis/releases/tag/v4.4.2
When specifying a postgresql connection uri like
postgres://username:password@host/dbname
The migrations fail with the (server side error):
Changing the uri to
postgres://username:password@host/dbname?charset=UTF-8
is a workaround to this problem, but sinceutf8mb4
isn't a valid encoding type for postgres, it shouldn't be necessary.The text was updated successfully, but these errors were encountered: