[mythtv] [PATCH] prompt before upgrading database

Jeremiah Morris jm at whpress.com
Mon Oct 18 14:01:39 UTC 2004

On 17 Oct 2004, at 8:15 AM, Andrew Dennison wrote:

> I recnetly had an "incident" where I ran a cvs version of setup on my 
> main system. The database schema was upgraded a few levels before I 
> had realised what I'd done:0
> Attached patch (dbcheck0.diff) makes setup prompt before it starts the 
> upgrade.
> dbcheck1.diff prevents mythbackend and mythfrontend from also updating 
> the db - forces you to run setup if db isn't up to date. This may? not 
> be acceptable so it's split into a separate patch.

I've had very similar "incidents" with a remote CVS frontend.  I see 
the value of having upgrades controlled by a single program, but setup, 
in its current incarnation, isn't quite right.  Setup isn't scriptable 
and needs a GUI, so I couldn't integrate it as part of my backend 
startup.  My master backend acts as a dedicated Myth box and doesn't 
even have a keyboard attached, so I don't want to connect up to it just 
to run setup.  Besides, one wrong keypress at the start of setup, and 
all your settings are wiped -- I've had one of these "incidents" too.

I'd like to see setup take an "--upgrade-only" command-line option, 
which does the DB upgrade but none of the other backend setup.  On a 
related note, a "--force" option to answer the beginning prompts with 
the default values ('yes' to upgrade, 'no' to the table clearing 
questions) would be useful too.  With those options and Andrew's 
patches, I can maintain a completely automatic backend without having 
my experimental OS X frontend break the database.

If this sounds like an acceptable solution for everybody, I can submit 
patches for the new options in setup.  What do you think?

- Jeremiah

More information about the mythtv-dev mailing list