""Aaron Stone"" <[EMAIL PROTECTED]> said: > Christian G. Warden <[EMAIL PROTECTED]> said: >> On Wed, Aug 25, 2004 at 06:39:09PM -0000, Aaron Stone wrote: >>> ""Christian G. Warden"" <[EMAIL PROTECTED]> said: >>> >>> > On Wed, Aug 25, 2004 at 06:30:04PM -0000, Aaron Stone wrote: >>> >> Eventually we should include a 'dbmail-check' or 'dbmail-upgrade' >>> >> (something like that) that reads out the schema, compares it to the >>> >> release schema, and performs the necessary ALTER commands to get it >>> >> up to date. >>> >> >>> >> To the best of my knowledge, no such tool exists :-\ >>> > >>> > mysqldiff and pgdiff should be useful. >>> >>> Both require fairly significant human parsing in order to generate >>> reliable upgrades, don't they? >> >> Perhaps. I used mysqldiff a while ago, and the SQL it generated wasn't >> ideal. It would drop columns that had changed and re-add them rather >> than modify them causing data loss. Nonetheless, it should at least >> point out the changes that need to be made. I've been running a pre-RC >> CVS snapshot of 2.0 since last year, so when I finally upgrade, I'll >> need something like mysqldiff to figure out what schema changes I need >> to make. > > The MySQL sources are available under GPL, so we could possibly just grab > a copy of the mysqldiff sources and hack on them until they become the > DBMail utility that we need.
Silly me, mysqldiff, phpmysqldiff and pgdiff are separate programs, none are written in C, and only pgdiff, which is written in TCL, is GPL. So basically if we build a utility to do this, we'll be working from scratch. By making the utility GPL and with a generic structure (not deeply DBMail specific) we'd be making a great contribution to the state of the art :-) Aaron --
