Changes between Initial Version and Version 1 of Ticket #32689
- Timestamp:
- Apr 27, 2021, 8:20:10 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #32689 – Description
initial v1 1 `makemigration` will generate infinite migrations if the callable path is miss-matched such that you end up with two discreet callable objects (I'm still trying to identify where exactly the migration framework is generating this missmatch ) then the same migration is generated every time you run the command which results in no actual change to the database.1 `makemigration` will generate infinite migrations if the callable path is miss-matched such that you end up with two discreet callable objects (I'm still trying to identify where exactly the migration framework is generating this missmatch, I can see the difference stepping through `MigrationAutodetector.generate_altered_fields` in the debugger but I'm not sure if the root cause is inside `generate_altered_fields`, another method on `MigrationAutodetector` or somewhere else entirely...) then the same migration is generated every time you run the command which results in no actual change to the database. 2 2 3 3 In my case it's from a custom field library being used as a primary key.