[mythtv-users] Database internals

[Jeff Breitner]

On Sat, Jan 4, 2014 at 10:28 AM, Gary Buhrmaster
<gary.buhrmaster at gmail.com>wrote:

> I presume that you know that the MythTV tables default
> to (and are technically only supported as) with the
> MyISAM engine.... (*)
>
>
Which means no foreign keys, one area where an inconsistent backup would
likely result in the cataclysmic fail on restore predicted on this 'chere
list.  And as you pointed out, it also doesn't support transactions which
means --single-transaction in mysqldump is, well...doesn't really do much
for myisam.

Which leaves mysqldump --lock-tables if you really really want to be safe.
Which I pointed out in a follow-up reply after moments of great concern
over my bashism.  But I don't use it because mythbackend has coredumped on
me when it gets denied writes.   I really don't want to hear the complaints
that the TV quit working when I want a database copy to work on fixing
something that annoys me.

If the discussion continues on whether mysqldump is safe or safer than the
Perl script, has anyone run diff on the two results?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140104/28c99b17/attachment.html>