[mythtv-users] mythtv dropping mysql???

[Gary Buhrmaster]

On Tue, Oct 21, 2014 at 2:33 PM, Simon Hobson <linux at thehobsons.co.uk> wrote:
....
> So I think people are a bit nervous that we'll lose direct access before the right tools are in place to replace it.

To a very large extent, that will be in the hands of
the community.  All else being equal, lazy is likely
to win.  Perhaps the community should insist that
any new tools use the (services) API, or document
why those APIs are not sufficient and define the
required features to allow them to use the formal
APIs(*).  All other contributions will be rejected as
not contributing to the communities push to move
forward to avoid a mad rush and scramble at
some (really unspecified) future date.  And if one
starts now, there need be no last minute scramble
(as there has been with some other recent 3rd
party commercial service changes).

The MythTV devs have given everyone a heads
up.  They are giving you their intent (which is
less precise than an actual plan, or a schedule).
I, for one, appreciate that I now know where I
should be heading.  Some companies only give
you 6 months to rewrite your code before their
next release (which breaks your code).  MythTV
has provided a time frame which is longer.  Use
that time wisely.  Or pay a price later.

Who is willing to take the "No direct DB access"
pledge, and how many are in the "My(SQL) way or
the highway" camp?

I will take the "No direct DB access" pledge.

Gary

(*) And if the requirement and features desired
are reasonable, and there is no (equivalent)
way to accomplish the objective, and the devs
do not provide it, then shame on the devs.
But, first, give them an opportunity to meet
the needs.