Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-20 Thread Wichert Akkerman
On 04/19/2012 07:43 PM, Michael Bayer wrote: If you've seen my recent talks you saw that I'm a little skeptical of what you're terming non-monolithic databases.Let's say this means, a database with a set of tables maintained by entirely different packages, but with the possibility of

multi-package schemas (was Re: [sqlalchemy] stucco_evolution 0.4 released)

2012-04-20 Thread Chris Withers
On 19/04/2012 18:43, Michael Bayer wrote: but with the possibility of dependencies between those tables. If I understand correctly, if we were dealing with sets of tables that didn't have any dependency, you wouldn't need a distributed migration tool, each package would handle migrations for its

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-20 Thread Michael Bayer
On Apr 20, 2012, at 4:52 AM, Wichert Akkerman wrote: That suggests that every package would have its own migration tool, which is not very practical from a sysadmin point of view. I am an upgrading an application I want to be able to run all necessary migrations for all components of an

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-20 Thread Jeff Dairiki
On Fri, Apr 20, 2012 at 03:44:55PM -0400, Michael Bayer wrote: The one thing that's needed as far as Alembic is concerned is the ability to control the name of the actual migration table per environment, this is a short feature add that's been sitting as an enhancement request for some time

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-20 Thread Michael Bayer
On Apr 20, 2012, at 6:52 PM, Jeff Dairiki wrote: On Fri, Apr 20, 2012 at 03:44:55PM -0400, Michael Bayer wrote: The one thing that's needed as far as Alembic is concerned is the ability to control the name of the actual migration table per environment, this is a short feature add that's

[sqlalchemy] stucco_evolution 0.4 released

2012-04-19 Thread Daniel Holth
stucco_evolution 0.4 has been released. It is a migration tool for SQLAlchemy that attempts to deal with packaged dependencies having their own migration scripts. Reading - as depends on, web application - openid package - users/groups package web application - users/groups package When asked

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-19 Thread Michael Bayer
If you've seen my recent talks you saw that I'm a little skeptical of what you're terming non-monolithic databases.Let's say this means, a database with a set of tables maintained by entirely different packages, but with the possibility of dependencies between those tables.If I

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-19 Thread Daniel Holth
On Thursday, April 19, 2012 1:43:59 PM UTC-4, Michael Bayer wrote: If you've seen my recent talks you saw that I'm a little skeptical of what you're terming non-monolithic databases.Let's say this means, a database with a set of tables maintained by entirely different packages, but

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-19 Thread Daniel Holth
So there you have it. It very well may be that there is exactly one use case for this package, but who doesn't need to keep track of users and groups? Other than that it does a passable job of applying hand-written linear database upgrades, and it is short. that it is, and the surprise

Re: [sqlalchemy] stucco_evolution 0.4 released

2012-04-19 Thread Michael Bayer
On Apr 19, 2012, at 3:20 PM, Daniel Holth wrote: So there you have it. It very well may be that there is exactly one use case for this package, but who doesn't need to keep track of users and groups? Other than that it does a passable job of applying hand-written linear database