On 07/16/2013 03:55 PM, Michael Still wrote: > On Tue, Jul 16, 2013 at 4:17 PM, Thomas Goirand <z...@debian.org> wrote: > >> Could you explain a bit more what could be done to fix it in an easy >> way, even if it's not efficient? I understand that ALTER doesn't work >> well. Though would we have the possibility to just create a new >> temporary table with the correct fields, and copy the existing content >> in it, then rename the temp table so that it replaces the original one? > > There are a bunch of nova migrations that already work that way... > Checkout the *sqlite* files in > nova/db/sqlalchemy/migrate_repo/versions/
Why can't we do that with Keystone then? Is it too much work? It doesn't seem hard to do (just probably a bit annoying and boring ...). Does it represent too much work for the case of Keystone? Thomas _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
