[mythtv-users] Saved position no longer working

[Michael T. Dean]

On 06/12/06 22:03, Stuart Larson wrote:

>>On 06/12/06 21:22, Stuart Larson wrote:
>>
>>>Myth frontend and backend running rev 9710 on .19-fixes branch.
>>>
>>>Strange thing started happening after I installed a second frontend - my
>>>saved positions for recorded programs are no longer working.
>>>
>>Sounds like someone might have used a newer version of Myth on a
>>frontend or backend.  The new version updated the database for the new
>>bookmark-handling, and the old version can't use it.
>>
>>>One thing I know I did in error was download, compile, install and run
>>>mythfrontend on revision 9710 of the main code branch (as opposed to
>>>.19-fixes).  I then uninstalled, and rebuilt from rev 9710 .19-fixes.
>>>Would this have corrupted tables at all?  Only thing I can think of is
>>>that it messed up the DB schema somehow..
>>>
>>Bingo.
>>
>>>or I'm missing something
>>>entirely easy to fix.
>>>
>>Roll back your database to your pre-upgrade backup to continue using
>>0.19-fixes.
>>
>Well, that was easy enough:
>
>mysql> ALTER TABLE recorded MODIFY bookmark varchar(128);
>Query OK, 460 rows affected (0.07 sec)
>Records: 460  Duplicates: 0  Warnings: 0
>
>*remembers to make backups more often*
>

Well, that's *one* of the changes you need.  0.19-fixes SVN r9710 uses 
DBSchemaVer 1123 and SVN head r9710 uses DBSchemaVer 1137 and made 
definition changes to capturecard, cardinput, recorded, channel, 
jumppoints, keybindings, program, and recordedprogram as well as data 
changes within many different tables.

Do you have any 0.19-fixes backups?  If not, you may want to sign up for 
the -dev and -commits lists and start reading them so you'll know how to 
work your systems after you upgrade to SVN head (r9710 or later).

The other option is to do an export of your current data as described 
at http://mythtv.org/docs/mythtv-HOWTO-23.html#ss23.5 and follow the 
instructions at http://mythtv.org/docs/mythtv-HOWTO-23.html#ss23.7 to 
get the important information and modify the INSERT's to work with the 
0.19-fixes schema.  Then, drop your database, create a new one, start 
mythtv-setup (version 0.19-fixes r9710) to get the appropriate schema 
version, exit mythtv-setup, and do an import.  However, because of the 
changes to recordedmarkup, I would recommend you ignore that table when 
getting the important information and just run "mythcommflag --rebuild 
--all" and "mythcommflag --all" after importing your data.  Note that 
with this approach, you'll have to figure out how to modify the INSERT's 
to get the right data in the right places for 0.19-fixes.

Any other solution is not clean and you'll likely have problems.  If you 
don't fix the issue properly, please keep this in mind before posting 
about "bugs" in Myth.  ;)

Good luck (and always make a backup before upgrading),
Mike