On Jul 1, 12:53 pm, Andrew Godwin <and...@aeracode.org> wrote: > > Ah, interesting. Alembic doesn't appear to support fully mutating SQLite > databases, which is the really gnarly part of the South code I'd love to > outsource. Looks like there's still plenty of work to be done no matter > what happens.
While I'm quite annoyed at the SQLite project itself for not supporting ALTER in a comprehensive way, especially given in SQLite4 they will have constraints enabled by default (note this makes SQLite's notion of rename->drop->recreate-copy impossible in many cases) I have accepted the feature request to add the "rename->drop- >recreate->copy" system into Alembic's SQLite module. It's already been done in SQLAlchemy-migrate so this is just one of those areas where we need a willing volunteer to help. Alembic contains primitives for all the DDL stuff otherwise, building on SQLAlchemy's extensible DDL/SQL construct system. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
