[mythtv-users] mythtv dropping mysql???

[Simon Hobson]

Michael T. Dean <mtdean at thirdcontact.com> wrote:

... a lot of good comments

> Imagine if, instead of writing some SQL to just stick values into columns in the DB (where you have to figure out which columns and either assume or look up the specific values to insert into those columns), you had a generic script you could run to manipulate your recording rules en masse--for example, it first lets you select a group of rules (either one by one or using a "query"--some criteria such as "user job 1 is enabled") and then apply a modification to those selected rules (such as "enable user job 2").  Such a script would be straightforward to write--the hardest part being the generic UI.  Now imagine if that functionality were available directly from the backend web server (the new "MythWeb" so to speak).  It seems that bulk changes to recording rules is a common-enough requirement that we /should/ have such a capability, but no one (dev or otherwise) has been motivated enough to write a UI for it since there's a lazy way out.

For all the good points - pretty well most of which I agree with BTW - I think a lot have this nagging feeling that while the idea is great (have a generic UI which allows people to manipulate stuff while enforcing database/schema rules), some of us can't help have this nagging feeling. Lets face it, it's a not inconsiderable task writing all that, and as developers are human it's only natural that they'll lack enthusiasm for the bits they don't need. That's not in any way meant to be a criticism - we're all human.
So I think people are a bit nervous that we'll lose direct access before the right tools are in place to replace it.

And there's a bit of "chicken and egg" as well, which you hint at. As long as there is an easy way out, then there isn't the impetus to create the proper way. So I can see there being an intermediate stage where direct access has gone, there's a lot of wailing that the sky's falling in, and eventually the tools will follow to fill in the gaps. But during that time, quite a few workflows that some of us rely on will be broken and we might not have ready access to the new tools to build our replacements.

I can see a bit of a comparison with when Apple launched the iMac. Many (myself included to a certain extent) wailed about the missing ADB and serial ports, and the almost complete lack of USB devices. I recall that around that time, most PCs and Windows had USB - but it was nicknamed Useless Serial Bus as there was nothing available to plug in.
But within months (or even weeks), there was a plethora of USB devices available. Now few even remember the old ports with their limited functionality - but there was pain and wailing during the adjustment period even though the end result was much better.


I get the impression that most aren't actually against an embedded DB - but they are worried about that interim situation.