On 10/3/07, Max Ischenko <[EMAIL PROTECTED]> wrote: > Hello Mark, > > On 10/3/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > > > I hadn't seen JJ's code, but migrate is a pre-existing, project which > > attempted to solve the same problem in a similar way. Migrate lets > > you use SQLALchemy to create your migration scripts in python, and > > adds a couple statements to SQLALchemy to make that easier. But, > > other than that (and the way the version repository is handled) the > > two projects look very similar. > > 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. ;)
SQL can't express a lot of things that you need when you're doing an upgrade, and can't easily express a lot more things that you need. Of course, if you can do it in SQL, doing it in SQL will be faster, and sometimes a lot faster. If I recall, there's already a "plain SQL" option for migrate upgrades anyway. Neil -- Neil Blakey-Milner http://nxsy.org/ [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
