On Wed, 2004-08-25 at 14:30, Aaron Stone wrote: > ""Matthew T. O'Connor"" <[email protected]> said: > > > Hello all, I just read the bug report about duplicate mailboxes getting > > entered, and the fix was to add a unique constraint to the database. > > Given all the SQL changes, and all the different RC's I think it's > > impossible to add conversion scripts for all these possibilities. > > > > What might be helpful instead is a tool that is updated every time > > someone makes a change to the schema of the database that verifies that > > the user's schema is totally correct. Major problems will be obvious, > > but missing unique indexes or wrong data types etc... will cause subtle > > breakages. > > This is essentially the holy grail of database upgrade systems. 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 :-\
I know, that's why I was NOT suggesting a magic upgrade tool, rather just a tool that lets you know that your schema is not exactly what it should be and perhaps letting you know what it thinks is missing.
