Migrate, the SQLALchemy migration tool has a new home and a new name. You can find the new improved sqlalchemy-migrate at:
http://code.google.com/p/sqlalchemy-migrate/ Jan Dittberner and dykang have done the nessisary work to get migrate back into a functional state for SQLAlchemy 0.3.10, and that work was merged into trunk today. There are plans to do the SQLAlchemy 0.4 migration as soon as possible and release a sqlalchemy-migrate packate that is 0.4 compatable. But right now we need people who are willing to test migrate on 0.3 and let us know if everything works -- in particular we need someone who has a full oracle licence to test and see if migrate works there (we have failing oracle test, but we're not sure if it's the result of 10g XE limitations, or if the oracle support is actually broken). There's a to-do list on the wiki at: http://code.google.com/p/sqlalchemy-migrate/wiki/Todo Any input/help/advice/critique from the community is welcome. When I talked about SQLAlchemy at PyCon the issue of Migrations was one of the most discussed features, and I would really like to see world class migration support in SQLAlchemy to go along with all of it's other world class features ;) -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
