cubicweb #4002156 remove_cube turns following add_cube into no-op [validation pending]
if a migration script contains 'remove_cube("foo"); add_cube("bar")', the add_cube may be turned in to a no-op. I think it's because remove_cube updates config.cubes() to something including new dependencies, which may not have been added to the db yet.
add followed by remove seems to work. that's ok if they're in the same script, but i can imagine cases where different cubes need to add/remove dependencies, in which case it's not as easy to work around.
|closed by||#e0e71b45bf8d [migration] don't add new elements to config._cubes in remove_cube|
|patch||[migration] don't add new elements to config._cubes in remove_cube [applied]|