I've implemented a fix for this that works, in which I deleted the
code that automatically drops the old primary key when a new one is
added. I think this is consistent with the way it's intended to be
used: if I autogenerate a migration for changing the primary key, then
the old one is explicitly
Hi all,
I've been looking at bug #28542, in which a migration can be played
forwards but not reversed. I think I can see what's happening, but I'm
not 100% sure what the right resolution is, so I wanted to get some
input.
The migration in question looks something like this:
# Start out with
