home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Uknown Error Occurred
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 915993" data-attributes="member: 82144"><p>It only happens to MySQL databases.</p><p>Without getting too technical, the issue is due to the fact that the MySQL table engine that we use (MyISAM) doesn't support transactions. Effectively, it can't handle doing multiple updates at once. Do a google for mysql myisam crash and you'll come up with plenty of info if you want to know more.</p><p><a href="http://dba.stackexchange.com/questions/15075/why-do-mysql-tables-crash-how-do-i-prevent-it" target="_blank">http://dba.stackexchange.com/questions/15075/why-do-mysql-tables-crash-how-do-i-prevent-it</a></p><p> </p><p>[edit: the MP designers of yesteryear chose MyISAM because it is supposedly faster than other MySQL table engines. I don't know if that can be proved. If you want to avoid this in future, use a Microsoft SQL Server DB. The express version is free. You could also try updating to a more recent version of MySQL.]</p><p> </p><p></p><p>Technically I'm not sure. In this case and in 90% of the cases I see, the Program table (which is the table that holds EPG data) is the table that crashes. Obviously EPG data is usually replaceable.</p><p> </p><p></p><p>It is not MP that is marking the table as crashed - it is MySQL.</p><p>MP does not have this insight. MP tries to do business as usual and finds that things that normally work don't, and so we spit out errors into the log file.</p><p>Technically there is a 3rd party layer between MP and the database, and if anything it would be that layer that would need to detect and report the problems.</p><p> </p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 915993, member: 82144"] It only happens to MySQL databases. Without getting too technical, the issue is due to the fact that the MySQL table engine that we use (MyISAM) doesn't support transactions. Effectively, it can't handle doing multiple updates at once. Do a google for mysql myisam crash and you'll come up with plenty of info if you want to know more. [url]http://dba.stackexchange.com/questions/15075/why-do-mysql-tables-crash-how-do-i-prevent-it[/url] [edit: the MP designers of yesteryear chose MyISAM because it is supposedly faster than other MySQL table engines. I don't know if that can be proved. If you want to avoid this in future, use a Microsoft SQL Server DB. The express version is free. You could also try updating to a more recent version of MySQL.] Technically I'm not sure. In this case and in 90% of the cases I see, the Program table (which is the table that holds EPG data) is the table that crashes. Obviously EPG data is usually replaceable. It is not MP that is marking the table as crashed - it is MySQL. MP does not have this insight. MP tries to do business as usual and finds that things that normally work don't, and so we spit out errors into the log file. Technically there is a 3rd party layer between MP and the database, and if anything it would be that layer that would need to detect and report the problems. mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Uknown Error Occurred
Contact us
RSS
Top
Bottom