Hello,
Another option that might or might not work would be to violate the rule and do
refer to "current" models during the migration to version X, but thereafter
reset your migrations and only support migration to X+1 from X, not from earlier
versions. This would need detailed release notes about
On Tue, Aug 29, 2017 at 1:43 PM, Matt S wrote:
> Standard practice is that you do not refer to "current" models (i.e. from
> app.models import MyModel) in a migration as the migration will break when
> that models changes. This means copying any model-specific code into the
> migration. This beco
On 30/08/2017 6:43 AM, Matt S wrote:
Standard practice is that you do not refer to "current" models (i.e.
from app.models import MyModel) in a migration as the migration will
break when that models changes. This means copying any model-specific
code into the migration. This becomes impractical
Standard practice is that you do not refer to "current" models (i.e. from
app.models import MyModel) in a migration as the migration will break when
that models changes. This means copying any model-specific code into the
migration. This becomes impractical when the code needed for the migration
4 matches
Mail list logo
