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?
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?
Marius Gedminas
--
It's my understanding that although in principle TCP can handle huge
throughputs in practice many stacks haven't been optimized for that case, so
you have to either use a utility which opens multiple TCP sessions in parallel
or do something really radical like upgrade to the latest version of the linux
kernel.
-- Bram Cohen
signature.asc
Description: Digital signature
