[mythtv-users] Saved position no longer working

[Stuart Larson]

> 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

Thanks for the information.  Unforunately, my "upgrade" was not
intentional.  I uninentionally downloaded, built and ran the wrong version
of mythtv to run as a frontend.  That, indeed, is my own fault.  I first
realized my error when mythfrontend told me my frontend was using a far
newer protocol, and the backend was using a much older one.

That is not a bug, that is my own fault.

At that point, it was too late (backups aside, of course). While having
automatic database schema updates is very, very nice (I upgraded to .19
with such), in retrospect, it would have been nice to be warned that it
was beeing done.

In any case, my "upgrade" was unintentional... my saved positions seem to
be working, and recordings seem to keep recording, and I'll keep any
future quirks to myself.

Thanks,
Stuart