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
Possible type mapping error in recent version #1238
Comments
+1 here with postgres, same issue INFO [alembic.runtime.migration] Running upgrade ec2f32c25f34 -> 7f6cdb3621f7, add data element support |
+1 here. same issue when using postgresql 15 as the backend db.
|
+1 master branch |
Same issue for us. We are only allowed to use Postgres and we cannot use MySql/MariaDb. This makes it impossible for us to use Querybook in any way. Please fix the issue or provide some workaround.. |
Built a custom image from Querybook image to workaround this issue. FROM querybook/querybook:latest
RUN sed -Ei 's/sa.Text\(length=[0-9]+\)/sa.Text()/g' /opt/querybook/querybook/migrations/versions/*.py |
Going from 3.17 to 3.20 gave us this error. I believe it's a mysql to postgres type mapping error - is there any soultion other than swithing to mysql?
The text was updated successfully, but these errors were encountered: