[mythtv-users] MythTV with MariaDB

[Michael T. Dean]

On 03/26/2013 09:06 AM, Gary Buhrmaster wrote:
> On Tue, Mar 26, 2013 at 3:55 AM, Kevon wrote:
> ....
>> Gary,
>> Thanks for the pointers. I have not yet switch mysql to InnoDB. All my
>> databases were created before the default switch to InnoDB (5.5 I
>> think). I never had a problem with MyISAM so didn't see the need to
>> switch. Do I need to switch over to InnoDB before installing MariaDB?
> No, but depending on when you installed your databases, you may
> have been running InnoDB tables (MythTV changed the creation to
> explicitly select MyISAM at one point, but depending on when you
> installed, upgraded, rebuilt, whatever, you may have had InnoDB
> tables; and I think the mythweather plugin depends on features
> that require an engine more advanced than MyISAM).

Yes, MythWeather tables use InnoDB.  All other tables in MythTV are 
supposed to be MyISAM.

If you created your database after MySQL changed the default storage 
engine to InnoDB, but before MythTV was updated to explicitly specify 
the engine (i.e. before 0.25***), you can do a partial restore of a 
backup ( 
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup 
) to fix the database "corruption".  The biggest problem with doing so 
it the requirement to reconfigure everything after the partial restore 
(which only restore recording rules and non-recreatable data, such as 
current recordings and recording history).

Mike