-
Notifications
You must be signed in to change notification settings - Fork 223
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
Postgres migration bug in 1.4.4 #2664
Comments
same for me on PostgreSQL 16.4 |
Is one of you able to edit this file: https://github.com/morpheus65535/bazarr/blob/master/migrations/versions/b183a2ac0dd1_.py#L24 And replace with this: Restart Bazarr and let me know if ti fixes the issue. Thanks! |
|
And if you use this instead in the file?
Thanks for testing out, I don't have a postgresql instance to test this. If it doesn't works, I'll deploy one but I would better use my spare time else where for the moment ;-) |
|
Could you show us the content of this table? |
Can you run this SQL to see if it fixes the column type and values properly?
|
That worked. I ran the sql:
I re-created the container to remove all the changes I did earlier to the migration scripts and it is now up and running. |
Should be fixed in upcoming beta. Let us know if it's not the case! |
@morpheus65535 Still no go for me :(
|
Upgrading from 1.4.3 to 1.4.5 I ran into this issue, using postgres. Running
as noted above fixed it. |
Describe the bug
Upgrading from 1.4.3 to 1.4.4 throws a postgresql error during migrations. Postgres is 16.2
The text was updated successfully, but these errors were encountered: