Hello Rich,
Unfortunately the migration framework is not smart enough to resolve this
kind of dependency.
The order of operation/migrations of the makemigrations is generated by the
autodetector which
hardcodes most of its logic.
I would have assumed that constraints were generated _after_
I've created a CompositeForeignKey constraint derived from Django's new
BaseConstraint. It requires that I manually make a unique_together in any
of the referenced models views due to the DB internal requirements of
composite foreign keys.
It mostly works -- except that when the operations
2 matches
Mail list logo
