Reply to thread

Message: <blockquote data-quote="CathodeRay" data-source="post: 1148095" data-attributes="member: 128074">Hi VasilichDoing things to MySQL databases always feels a bit like holding a stick of dynamite in one hand and a lighted match in the other and hoping nothing goes wrong. However I have converted all the tables in mptvdb from MyISAM to innoDB (I used HeidiSQL, have to do each table individually, can be done using sql but more chances for errors through typos) after backing up mytvdb. No error notices, and the table sizes increased (as I believe is to be expected). I haven't changed anything else, MyISAM is still the default engine in my.ini for example, but I think that only kicks in for new tables as they are created. On first reboot MySQL had started by the time I had services.msc open and tvservice started soon after, MP started normally and all the expected data - channels, EPG, Recorded TV etc was as expected. So I think your suggestion may have fixed the problem - if so many many thanks.Perhaps (I'm speculating here) when I did the auto-repair (or even more so the database rebuild, given the setting in my.ini), I managed to end up with MyISAM tables when previously I had had innoDB tables? Not sure how or why unless I changed them to inniDB so long ago I've forgotten, but it seems a possible explanation: until last week they were innoDB, then got reset to MyISAM.Lehmden - "it was getting worse with every new version of TVServer..." - this is one of the reasons why I tend to stick with the old (ancient) version I have. I tried upgrading a couple of times and things got worse not better. If it works, why fix it... I also agree that MySQL tends to be the database from Hell (there are other setting I have to use it in, and it often provides lots of fun and games) whereas sqlite more often than not just simply works.Many thanks to all who have so generously helped sorting out this problem which I hope is now fixed.CathodeRay</blockquote>

Verification