[mythtv] Schema updates

[Simon Kenyon]

f-myth-users at media.mit.edu wrote:
>  Yeah, it's that latter issue that worries me.  We had a "near miss"
> here a few months ago (though I'd been worried about it from the
> start) where somebody who -did- have authorization to use our backend
> (and thus had its IP address and DB password---after all, he was
> working with us :) very nearly blew it by running a newer frontend.
> And really, it wouldn't have been his fault at all---he'd just
> "downloaded Myth" and (almost) tried to run it.  Oops.
>
> [Unless I revved the backend the day a new release came out, there'd
> always be a window when that could happen, even if people around here
> never used SVN.]
>
> But if we can figure out if there -is- a solution everyone can live
> with, that'd be a great start on this issue.
>   
how about the "ruby on rails" solution?
every db "upgrade" script also has an associated "downgrade" script
--
simon