[FIX] alembic migration #1178
[FIX] alembic migration #1178
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
| if ( | ||
| type_ in {"index", "constraint"} | ||
| and name.startswith("pe_") | ||
| and (name.endswith("_hnsw") or name.endswith("_dims_chk")) |
There was a problem hiding this comment.
include_object now unconditionally calls name.startswith for any index or constraint. Alembic invokes this callback with name=None for metadata constraints or indexes that were defined without an explicit name. When such objects exist, flask db migrate will crash with an AttributeError before generating migrations, blocking schema changes. Check that name is truthy before using string methods or handle unnamed objects separately.
Useful? React with 👍 / 👎.
attempt to not try to remove the auto-generated partitioned table.