On Mon, May 17, 2010 at 9:49 PM, Kent <[email protected]> wrote: > Ideally, I agree. Practically speaking, though, we came from a > company where dozens and dozens of developers worked on the system and > it was structured exactly this way (a master file and a series of > incremental upgrade scripts). It was always getting messed up between > the two sets of schema definitions until eventually we developed a > schema comparison tool and all those problems seemed to vanish. > > I'm obviously not saying SQLAlchemy needs to provide this, but just > trying to make a case for its usefulness. Thanks for your input.
I'v never tried it, but maybe miruku is what you are looking for: http://bitbucket.org/gjhiggins/miruku/wiki/Home -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
