[mythtv-users] mySQL problems

[Nick Veitch]

You can disable it by adding
skip-innodb
to your /etc/mysql/my.cnf file. This is also where you can stick the
innodb filepath as well if you do want to use it.

Did you build it from source? Most of the package versions don't enable
innodb by default, although the standard mysql source does.
While the transaction-safe capabilities might be handy in the case of
sudden power failures, there is a slight overhead associated with it. I
would personally stick with myISAM, but that may just be because I'm
more familiar with it...

Nick Veitch




Shawn wrote:

>
> Hello,
>
> I am just starting with mythtv and so aren't sure what the problem you 
> described was.
>
> I do use mysql though.  The mysql docs say  "InnoDB provides MySQL 
> with a transaction-safe (ACID compliant) storage engine with commit, 
> rollback, and crash recovery capabilities" and "From MySQL version 4.0 
> the InnoDB storage engine is enabled by default. "
>
> I use 4.x but not InnoDB and have never set anything related to it and 
> it has worked just fine.  AFAIK though it shouldn't be necessary to 
> have that for mythtv.  In fact, my tables are all MyISAM.
>
>> Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
>
>
> Anyway, the link below will explain how to deal with the InnoDB 
> aspects of mysql.  I would think you could disable it...
>
> see http://www.mysql.com/doc/en/InnoDB_start.html
>
>------------------------------------------------------------------------
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users at mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>  
>


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. 

The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. 

Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring.