On Tue, Mar 22, 2011 at 1:35 PM, Michael Bayer <[email protected]> wrote: > On Mar 22, 2011, at 12:44 PM, jaypipes wrote: > >> Hello all, >> >> I've decided to post here because bug reports and the mailing list for >> sqlalchemy-migrate don't seem to be monitored any more... > > I don't see a post regarding this issue at > http://groups.google.com/group/migrate-users , have you tried posting ?
I posted there. Awaiting moderation. > There's not much chance anyone on the list here would have any way of > helping. In particular migrate does a lot of hacks to make "migrations" on > SQLite work. I don't think it's a migrate problem. I think it's a SQLAlchemy problem. In the case when SQLite is the engine, a Table() object constructed with a new MetaData() before and after a SQL script is executed against the database will not show the changes to the schema, while it does when MySQL is the engine. If you look at the test case in my post, you'll see it's SA stuff I'm executing along with SA-Migrate stuff. The migration is shown to complete successfully. It's the SQLAlchemy Table() constructor that isn't working properly and noticing the changes to the underlying schema. Does SQLAlchemy basically just "punt" when it comes to DDL changes? -jay -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
