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 agree that fully automatic database migrations is a bad idea, but I also think having a standard way to make database upgrade scripts, track database versions and automate the running of those update scripts is very useful. I think migrate, or JJ's code would be particularly helpful when multiple programmers might be updating the same schema, and there are potentially deployments of multiple versions of the database, and all of that needs to be handled properly. --Mark On 10/3/07, Max Ischenko <[EMAIL PROTECTED]> wrote: > Hi Mark, > > I haven't heard about it yet but I presume it's about automatic database > schema updates? > > I do not believe database schema changes should or could be automated but > good luck with the project. > > For a start, I would be delighted to see something akin to jj's helpers to > be available for TG/Pylons projects: > http://jjinux.blogspot.com/2007/08/python-database-migrations_07.html > > Max. > > > On 10/2/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > > > > > I thought this might be of interest to many of you. > > > > We've been trying to gather up a few people to and revive the > > floundering SQLAlchemy migrations project. There's actually some > > pretty good code there already, it just needs a bit of love and > > tenderness to get it up to date wth SQLALchemy 0.4. > > > > It would be a huge benefit to have a clear story to tell in the python > > world about how to do agile database development, or just how to > > manage database upgrades as your application evolves. > > > > If you feel up to it, join the mailing list, > > ([EMAIL PROTECTED]) look over the code, ask some > > questions, and get involved. > > > > --Mark > > > > ---------- Forwarded message ---------- > > From: Mark Ramm <[EMAIL PROTECTED]> > > Date: Oct 2, 2007 11:39 AM > > Subject: Re: Migrate: svndump loaded into google code project? > > To: [EMAIL PROTECTED] > > > > > > > I just loaded Evan's svndump into the shiny new google code repository > > > at: http://sqlalchemy-migrate.googlecode.com/svn/ > > > > > > Now everything is ready to start the work on reviving migrate. > > > > Thanks Jan! > > > > Just a reminder, I think we should work on getting the monkey patch > > removal branch working with 0.3.10 first. > > > > I think someone may have even completed this work, if so now would be > > a great time to check that in. ;) > > > > Once that's done I would propose moving that branch to trunk and > > working on making it 0.4 ready. > > > > --Mark > > > > > > -- > > Mark Ramm-Christensen > > email: mark at compoundthinking dot com > > blog: www.compoundthinking.com/blog > > > > > > > > > -- 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 "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 -~----------~----~----~----~------~----~------~--~---
