[mythtv-users] INSERT INTO recordedmarkup fails w/duplicate; recording status changes
Gary Buhrmaster
gary.buhrmaster at gmail.com
Mon Apr 10 05:06:27 UTC 2023
On Sun, Apr 9, 2023 at 10:16 PM Ross Boylan
<rossboylan at stanfordalumni.org> wrote:
> 2. Databases are supposed to be corruption resistant, though
> mysql/maria may be less so (I know that used to be true).
The default (and supported) DB engine for
MythTV is MyISAM, which, explicitly, is NOT
crash or corruption resistant.
On a long term TODO list of some devs is
to verify/validate that MythTV works (for
MariaDB) with Aria (with is a corruption
resistant alternative to MySAM with high
MyISAM compatibility), or InnoDB (which
has some differences with MyISAM that
need to be considered).
Personally, I have moved all my DB tables
to InnoDB, but I have also played DBA in
past lives, so know how to carefully tune
and adjust the result (MyISAM, as used for
MythTV, is basically a set and forget solution).
My database is technically considered "corrupt"
by the project's definition (wrong DB engine),
so I can never, ever, ask for assistance on
this list, and I will never ever do so. If you
are not tall enough to ride the ride and do the
same, do not follow my approaches.
As Oracle (reportedly) pays Canonical to
promote MySQL over MariaDB in their
distro, and Ubuntu is reported to be the
most common OS for MythTV (which
may not reflect actual usage but just
reporting, but we do not know the full
truth), InnoDB may be the better choice
if and when some dev decides to
prioritize the validations even if Aria
could mean less work for a dev.
More information about the mythtv-users
mailing list