© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I don't think there is a straightforward way to fix cases like this where we end up with two distinct databases in the wild (one with the column, one without).
I propose that we add the ALTER TABLE to the top of these two upgrade files, outside the transaction, with a notice saying it is alright if it fails. Anyone who was able to run these upgrades successfully must already have this column, so going this route should help those who need it while not harming those who don't need it.
Then we re-roll a 2.5.3"b" with the fix in place. Thoughts?