Feature #4728

Remove databases after upgrade

Added by Laurent Opprecht over 7 years ago. Updated about 7 years ago.

Feature implemented
Target version:
Start date:
Due date:
% Done:


Estimated time:
SCRUM pts - complexity:


What do we do with course databases after migrating to a unique db?
I would be inclined to have the installation script deleting them as we have quite a lot.

Associated revisions

Revision 577e6d6d (diff)
Added by Laurent Opprecht over 7 years ago

Remove databases after upgrade see #4728



Updated by Yannick Warnier over 7 years ago

  • Target version set to 1.9 Stable

I think we should offer a single script to drop them, apart from the upgrade script, and leave a message at the end of the upgrade. Technically, we should be able to make enough tests before the stable to avoid any problem, but I would really hate to see a real problem and then have flocks of beginner admins cry because they lost data.


Updated by Laurent Opprecht over 7 years ago

  • Assignee set to Laurent Opprecht

Agreed, this make sense for the admin to check first.
I intend to add it to the admin screen under the system block.


Updated by Laurent Opprecht over 7 years ago

  • % Done changed from 0 to 80

Need to add the translation ids to and to translate them.


Updated by Yannick Warnier about 7 years ago

  • Status changed from New to Feature implemented

Translation variables have been added and the feature works as expected.

Also available in: Atom PDF