On Mon, May 31, 2010 at 11:51 AM, Steve Singer <ssinger at ca.afilias.info> wrote:
> The idea is that you use a mixture of views and triggers to have 1
> schema that can be used by both versions of the applications that expect
> different schemas.  You then upgrade all your applications and then you
> swap the schema out to one that only has support for the newer version
> of the application.
>
> This sounds like a lot of extra work

We regularly do this; however we limit the changes between releases.
Sometimes we'll do two or three releases within a week just to do the
migrations of the database.

Since we run our system as a service, there is really only one live
copy to worry about, not a bunch of copies at customers' sites.