[mythtv-commits] mythtv commit: r15980 - in branches/release-0-21-fixes/mythtv by cpinkham

mythtv at cvs.mythtv.org mythtv at cvs.mythtv.org
Wed Feb 13 07:27:57 UTC 2008


      Author: cpinkham
        Date: 2008-02-13 07:27:57 +0000 (Wed, 13 Feb 2008)
New Revision: 15980
   Changeset: http://cvs.mythtv.org/trac/changeset/15980

Modified:

   branches/release-0-21-fixes/mythtv/libs/libmyth/dbutil.cpp
   branches/release-0-21-fixes/mythtv/libs/libmyth/dbutil.h
   branches/release-0-21-fixes/mythtv/libs/libmyth/mythcontext.h
   branches/release-0-21-fixes/mythtv/libs/libmythtv/dbcheck.cpp
   branches/release-0-21-fixes/mythtv/programs/mythfrontend/main.cpp

Log:

Carry over [15979] from trunk.

Various changes related to the new DB backup and Schema version check code.

- Add helper functions in dbcheck.cpp for locking and unlocking the
  schemalock table

- Add DBUtil::IsBackupInProgress()

- Break out the schema version check code in mythfrontend into its own
  function called CheckSchemaVersion().

- Modify CompareTVDatabaseSchemaVersion() to lock the schema before querying
  the schema version.  This is so that we always get the correct schema
  version.  If the DB is in the middle of an upgrade, we could get the wrong
  version.  By attempting to lock the schemalock table, we are blocked until
  the upgrade finishes, then the value we get back is the current, upgraded
  schema version.
  
- Modify mythfrontend so that when DB Upgrade expert mode is disabled and the
  schema needs to be upgraded but the frontend can't do the upgrade, the
  frontend will now wait a few seconds to see if a schema upgrade is
  initiated by another process.  If the upgrade is started, then mythfrontend
  will wait for the DB upgrade to complete before continuing, otherwise
  mythfrontend will timeout and display the exising message telling the user
  they need to run mythbackend or mythtv-setup to upgrade the DB.






More information about the mythtv-commits mailing list