-
-
Notifications
You must be signed in to change notification settings - Fork 689
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
Alembic migration generated always set enum nullable to true #466
Comments
You can reuse ChoiceType and set
Or, just to rewrite a single |
Thanks for your reply @bvsn however my plan is to make it working from model.py files and try to reduce customisation in migration files. |
Thanks for the report! This is because I just added #681 to make sure that that combination of parameters is not allowed. When Also, there was recently a fix for enums, so you should be able to use the enum directly, without a |
Assuming the original need was handled, this will be automatically closed now. But feel free to add more comments or create new issues or PRs. |
First Check
Commit to Help
Example Code
Description
alembic revision --autogenerate -m "MIGRATION MESSAGE"
Note: I have tested using sqlalchemy defination, and it is working but not for SQLModel.
Operating System
macOS
Operating System Details
No response
SQLModel Version
0.0.8
Python Version
3.10.5
Additional Context
No response
The text was updated successfully, but these errors were encountered: