I'm still using it ;-) My program just calls stucco_evolution.create_or_upgrade_packages(connection, 'myprogram.name') when it starts to create or upgrade my program's tables and all of its dependency tables. I think stucco_evolution is unique in allowing separate database-creating packages to depend on each other as a directed acyclic graph, and it's about 200 lines of fairly dense but ~100% statement coverage tested code. You decide: https://bitbucket.org/dholth/stucco_evolution/src/tip/stucco_evolution/__init__.py
If you don't want to automatically upgrade the database whenever possible then you would of course put the create_or_upgrade_packages() call in a script. Application startup would perhaps compare myprogram.name.evolve.VERSION to what's in the db. I have been using SQLAlchemy for years. stucco_evolution was not a self-teaching exercise in how to program SQLAlchemy. stucco_evolution still doesn't depend on Pyramid in any way. I'm not aware of any stucco_evolution users besides myself. Is anyone else using it? -- 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.
