[mythtv] [mythtv-commits] mythtv commit: r21955 - in trunk by cpinkham

Chris Pinkham cpinkham at bc2va.org
Sun Sep 20 02:32:35 UTC 2009


I forgot to mention in my commit log that this patch does touch the
MYTH_BINARY_VERSION, so you'll have to do the normal big recompile again.

Since we _know_ everyone running trunk is also reading -dev, then I'm
sure they'll see this message. :)

* On Sun Sep 20, 2009 at 02:29:46AM +0000, mythtv at cvs.mythtv.org wrote:
>       Author: cpinkham
>         Date: 2009-09-20 02:29:45 +0000 (Sun, 20 Sep 2009)
> New Revision: 21955
>    Changeset: http://cvs.mythtv.org/trac/changeset/21955
> Modified:
>    trunk/mythplugins/mythmusic/mythmusic/dbcheck.cpp
>    trunk/mythplugins/mythvideo/mythvideo/dbcheck.cpp
>    trunk/mythtv/libs/libmyth/dbutil.cpp
>    trunk/mythtv/libs/libmyth/dbutil.h
>    trunk/mythtv/libs/libmyth/schemawizard.cpp
>    trunk/mythtv/libs/libmyth/schemawizard.h
>    trunk/mythtv/libs/libmythdb/mythversion.h
>    trunk/mythtv/libs/libmythtv/dbcheck.cpp
> Log:
> Fixes some confusing DB schema upgrade messages in the SchemaUpgradeWizard
> by adding a string that gets printed in the logs to indicate which schema
> we are checking.  Currently only MythTV, MythVideo, and MythMusic are
> using the schema wizard, but the log messages could be confusing when the
> relatively low MythVideo and/or MythMusic version numbers were printed out
> with the same format message as the higher MythTV schema version number.
> All messages should now have 'MythTV', 'MythVideo', 'MythMusic' in them.
> Modify the schema wizard and DB backup util's BackupDB() methods to return
> an enum instead of boolean.  Now we can distinguish whether a backup
> was made, failed, skipped for empty DB, disabled, etc..  The schema wizard's
> screen is now fixed to show the proper message based on the DB upgrade
> status.  Previously we would tell the user a backup was located in an
> empty location if they had backups disabled (including Windows users where
> backups are hardcoded to be disabled).
> Fix a few places where we were manually upgrading the DB schema version
> rather than using the performActualUpdate() routine.  This meant that in
> a few places, we weren't displaying the 'Upgrading to schema version X'
> message for that specific version upgrade.  These messages are now
> printed manually in the upgrades that bypass performActualUpdate().
> _______________________________________________
> mythtv-commits mailing list
> mythtv-commits at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


More information about the mythtv-dev mailing list