[mythtv-users] mythtv dropping mysql???

Michael Watson michael at thewatsonfamily.id.au
Tue Oct 21 06:47:36 UTC 2014


On 21/10/2014 12:55 PM, Michael T. Dean wrote:
> And it will be possible for you to access the "full raw data".  It's 
> still a MySQL database file.  We're just saying we're not going to 
> make people install the MySQL server to use it. 

If its just going to be an MySQL database file sitting in a folder 
somewhere, then someone could simply point a MySQL Server to that file, 
and really fubar the database if they left the MythDB engine running at 
the same time, maybe file locks will prevent this, but where there is a 
will, there's a way....

Recently there has been a little bit of chatter about optimising MySQL 
for MythTV, and how much of a difficult task it is, I wonder how Myth 
(with embedded MySQL/MariaDB) will achieve this, or will there be more 
config variables to cater for this.  If more config variables are added, 
brings me back to wondering why the DB needs to be embedded.  Is it 
merely to prevent the odd user from destroying there database, or simply 
to prevent the odd user difficulty in setting up MythTV - A Firstime 
Myth User, is far better to try installing MythBuntu (or one of the 
other dedicated distro's) than to try compiling/installing themselves, 
but then if a user can compile Myth by themselves, surely they can 
configure a DB server by themself.

Is it that, it has come a time that MythTV needs a consistent DB engine, 
much like the need for a consistent ffmpeg version.  Are the differences 
in DB engines becoming to great across distros/platforms?

Lets say, I want to enable/disable User Job 1 on all existing recording 
rules, currently through the frontend or mythweb this is a painfully 
slow process with more than a handful of rules.  Does the framwork 
currently exist in Perl/Python Bindings or Services API to achieve this 
operation?    An example of how something like this can be scripted 
using the "proper" tools, could help me and others to use the proper 
tools rather than resorting to "lazy" SQL commands.


Michael Watson



More information about the mythtv-users mailing list