[mythtv] [mythtv-commits] Ticket #4013: Prompt before upgrading database schema

Isaac Richards ijr at case.edu
Wed Sep 26 17:49:19 UTC 2007

On Tuesday 25 September 2007 11:38:07 pm Nigel Pearson wrote:
> > I'm not sure about the 'Use old schema' option - that's too likely
> > to corrupt
> > things, I'd think.
> most things are still safe because they
> cannot actually talk to the backend.

That doesn't check the DB version, does it?  I don't think it does, so it 
really wouldn't prevent a frontend from breaking the DB..

> It may still cause problems, but I wanted a
> way to allow newer frontends to at least run.
> e.g. Someone brings over a new LiveCD or their
> laptop to demonstrate a new plugin or feature.
> You graciously let them connect to your database,
> but not do anything dangerous like scheduling or
> editing recordings.
> If you are still uncomfortable, maybe a second
> OkPopup after the user selects "Use old..." ?

How about a command line option to connect, 
instead?  --really-connect-to-old-db-version-i-know-it-might-break-everything

Or something like that.. =)

> > Actually, it might make more sense to just pop up a message and say
> > 'Please
> > run mythtv-setup on the master backend to upgrade the schema', and
> > refuse to
> > run until that's done.
> Possible, although the current ability to upgrade
> from several programs is a lot simpler?

I suppose, but maybe check that, if run from the frontend, no backends (or at 
least the master) are currently running?  And maybe a second level 
confirmation that the upgrade will happen?


More information about the mythtv-dev mailing list