On Thu, 2010-12-09 at 03:12 +0200, Marius Gedminas wrote: > Inspired by > http://blog.cherouvim.com/a-table-that-should-exist-in-all-projects-with-a-database/ > > What's a good way to manage schema migrations in a Pyramid project?
Daniel may murder me for mentioning it (I don't know if he intended it for public consumption), but he wrote this: http://bitbucket.org/dholth/stucco_evolution/src It is a plugin to http://docs.repoze.org/evolution/ for SQLAlchemy. > SQLAlchemy Migrate is a promising tool for RDBMSes. What would be a > nice way to integrate it? "Nice", in my book, means things like having > > paster serve myapp.ini > > check on startup if the database schema is recent enough and either > perform the necessary migrations automatically -- if the .ini file > allows this -- or abort and tell me what commands to run to perform the > migrations manually. > > Last time I tried SQLALchemy Migrate on a Pylons project, I hit a fog of > confusion (what migrate commands do I need to run when, exactly?), and > then, eventually, a brick wall (in the sense of various changes being > unsupported with sqlite, which I wanted to use during development, for > simplicity). I ended up filing a bunch of issues and reinventing my own > bicycle. I see that sqlite support is much improved nowadays. > > Similarly, when you're using ZODB with Pyramid, is there something like > zope.generations for it? repoze.evolution is basically the guts of zope.generation. - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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-discuss?hl=en.
