MySQL and InnoDB - any pitfalls (1 Viewer)

[CX23882-19]

Since the latest Microsoft Guide data screw-up, I have decided to move completely over to MediaPortal, after trialling it on a secondary PC for some time. So far I'm happy with it.

I have gone with MySQL for now. I notice that the tables created by MediaPortal use the MyISAM engine - are there any pitfalls to be aware of if changing this to InnoDB? I've never felt comfortable with MyISAM on a UPS-protected server, let alone a living room HTPC which could get unplugged by mistake.

The main thing I wanted to check is that there aren't any features being used by MP that require MyISAM (e.g. FullText index) so I'm good to go in converting it.

 

[Holzi]

Since the latest Microsoft Guide data screw-up, I have decided to move completely over to MediaPortal, after trialling it on a secondary PC for some time. So far I'm happy with it.

I have gone with MySQL for now. I notice that the tables created by MediaPortal use the MyISAM engine - are there any pitfalls to be aware of if changing this to InnoDB? I've never felt comfortable with MyISAM on a UPS-protected server, let alone a living room HTPC which could get unplugged by mistake.

The main thing I wanted to check is that there aren't any features being used by MP that require MyISAM (e.g. FullText index) so I'm good to go in converting it.

There is a mantis entry scheduled for MP 1.3.1 to do this -> Use InnoDB as default MySQL engine
If you know how to convert it maybe you could help us and do some tests?
Thanks!

 

[CX23882-19]

I have converted the tables to InnoDB and nothing has immediately broken. Is there anything in particular which needs closer scrutiny?

 

[seco]

I have converted the tables to InnoDB and nothing has immediately broken. Is there anything in particular which needs closer scrutiny?

Although I don't know anything about TVServer SQL queries, I would look into general performance of EPG views (but I guess you need to have hundreds, maybe thousands of channels). Same goes with Recording views & I guess scheduling recordings (again I believe that seeing any difference would required thousands of records).

 

[Paranoid Delusion]

I switched over to MySQL5.5 a few weeks ago, which uses InnodDB as default, and certainly have not seen any obvious difference with 77 channels + 150 recordings enabled, as seco said, with a couple of thousand channels, which to me is the extreme end, there may be some slow down, but for the average user, I think reliability comes first, which InnoDB gives.

 

[regeszter]

I switched over to MySQL5.5 a few weeks ago...

Is there any plan to change the mysql version to 5.5?

 

[Paranoid Delusion]

Not currently, just as a side note MySQL5.6 has even more safety protocols in place for InnoDB, but that is still work in progress.