> I see then. > > Though I still don't see why it needs to be coupled to SQLAlchemy and why > you need python scripts instead of plain old SQL files. At least, that's the > solution I chose for my developers.org.ua codebase. ;)
Well, using python has some advantages over raw SQL. You can do data transformations as part of an update that either aren't possible or are very hard to do in raw SQL (imagine pulling zip code out of an single "address" field with regular expressions, etc). And (at least theoretically) you can write update scripts that work on multiple database platforms, so if you have some clients on MySQL and others on Postgres, you can write one update script that works for both. But it's true that raw SQL also has advantages. Migrate supports both. On the other hand, supporting both comes with extra complexity, and the simplicity of JJ's script is very nice. My main goal here is just to keep Migrate from dying unnecessarily -- lots of people seem to want this functionality, and some of them are willing to work on the project. I'd also be very happy to see JJ's script continue to live and gain a stronger user base. It's simple, handy and very lightweight. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
