I would say that a command to re-optimise a single migration would be a
good idea, especially since it needs no changes to the stored set of run
migrations since it would theoretically do the same thing.
Andrew
On Mon, Oct 31, 2016 at 1:58 PM, Shai Berger wrote:
> Hi,
>
>
Hi,
I'm doing some migration squashing, which was long overdue; so, I'm squashing
dozens of migrations at once. Within these migrations, there are data
migrations (RunPython operations) which, of course, stand as barriers to
optimization. The operations have not been defined elidable --