This thread is of interest to me as well, although the problem I'm
facing is somewhat different. Just to expand the space a little, here's
my situation:
- A legacy database schema with hundreds of tables and procedures.
- An application that accesses the database, with occasional updates
We will definitely also need a migration tool. We've only briefly
looked into the sqlalchemy-migrate tool, but were immediately
disappointed in its apparent requirement to keep versions of the
schema.
In our book, we see the ideal tool as one that doesn't care about
versions: it just looks at the
there's a tool for Django called South that does this. But personally I think
writing a few lines of alter_column() is preferable to a heaping dose of
schema-guessing magic.
On May 17, 2010, at 3:28 PM, Kent wrote:
We will definitely also need a migration tool. We've only briefly
looked
On Mon, May 17, 2010 at 9:49 PM, Kent k...@retailarchitects.com 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
Thanks, that looks like its conceptually what we are hoping for, at least.
On 5/17/2010 3:58 PM, Tamás Bajusz wrote:
On Mon, May 17, 2010 at 9:49 PM, Kentk...@retailarchitects.com wrote:
Ideally, I agree. Practically speaking, though, we came from a
company where dozens and dozens of
