|
|
|
|
|
|
by MythicDev
2143 days ago
|
|
|
As far as I know, this is by design; your migrations are supposed to operate on a frozen state of what your models and code _were at a point in time_. If you would rely on code outside of said migration, you would be breaching that frozen state and potentially end up with unintended side-effects (e.g. running a migration created 2 years ago that imports your code that changed today). This is why you might have to sometimes copy-paste logic to your python migrations, but you also guarantee that the migration always runs the same way. |
|
|