I set up the PyMigrate files on http://code.google.com/p/pymigrate/ without any tests because PyMigrate at that time was a prototype. I’ve created and refactored PyMigrate into a solid form and there the tests are included and these will continue to be maintained.

I haven’t written the tests to the library files yet because Pete’s comment about other libraries, and the sqlalchemy-migrate egg got me thinking. I’m thinking that since SqlAlchemy already supports multiple database types why should I re-invent that using a multitude of plug-ins? Why should I take on the maintenance responsibilities for doing so.

Nay I say. I’m thinking about using SqlAlchecemy exclusively, and it can deal with all the database types and queries. I’ll just create an adapter to work with it from my format.

Thoughts?

Tags: PyMigrate

I’ve made a couple of posts about how Python lacks the ability to use the Ruby on Rails like ActiveRecord:Migration and how I have come up with a way to incorporate such an idea. Well today is the 9th and I have finally released what I have.

You can find it here: http://www.techraving.com/pymigrate-activemigration-for-python/

Tags: database, migration, Python, ruby on rails

I just wanted to give you all a quick update. I’m still trying to get the release of the multi-database adapter migration assistant out for Python frameworks out. It’s a non-technical issue for now. Hopefully resolved soon.

As I’ve offer to everyone a chance to name it still feel free to do so. Only four days left to name it!

Tags: Python, rails migration