[mythtv-users] Upgrade issues.
Michael T. Dean
mtdean at thirdcontact.com
Sun Mar 29 03:58:29 UTC 2009
On 03/28/2009 09:25 PM, Robert McNamara wrote:
> On Sat, Mar 28, 2009 at 6:18 PM, Marc Tousignant wrote:
>
>> Also, I think the upgrade path should be fixed so that you don't have to
>> delete any tables.
>>
> This only occurs if you have broken/corrupt tables. It's not par for
> the course. Michael Dean tends to be the expert on the DB corruption
> issues, though, and has put a ton of work into saving people who have
> such corruption from heartache. It might not be perfect, but you
> wouldn't have wanted to try before he started. ;)
Yep, Marc, you're running a system (and I'll lay odds it's a Gentoo
system) where your DB server was misconfigured, so all the data getting
written into your DB was corrupted when you were using 0.21-fixes and below.
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding
If you had applied the patch on #5070 (
http://svn.mythtv.org/trac/ticket/5070 --after all, you did read up on
the -dev and -commits lists to catch up on all the discussion since 0.21
was released before upgrading, right?), it would have stopped the
upgrade and told you to fix your DB. So, when 0.22 is ready, it will
contain that patch or something better and people with broken DB's won't
import broken data--worst case, they'll be told their DB's are messed up
and given instructions to fix them. Or, if the Gentoo packagers are
feeling really nice, they'll script the fix for them.
Oh, and unless you have a pre-upgrade backup
(pre-all-your-messing-with-it-and-deleting-data-from-tables, ideally),
it's too late to fix your data. In a year from the upgrade, most of the
garbage will get cleaned out, but you'll have some that sticks around
for longer. (Not really worth worrying about, at this point, though.)
Mike
More information about the mythtv-users
mailing list