> What about calling the attribute something like "constraints" similar to
> how it's done in SQLAlchemy [1]? For now the attribute can just contain a
> list of Index() instances but that would also lay grounds for supporting
> check constraints and other related table level options.
>
Since
I was assuming that the Index class would be responsible for
generating the whole SQL. Seems like this isn't the case.
I assumed something like this would happen when a new index is added:
1. User adds a new BTreeIndex to a model
2. The makemigrations command detects a change and creates a
m
