<p dir="ltr"></p>
<p dir="ltr">please excuse brevity and pistakes as this email was composed on a mobile phone.</p>
<p dir="ltr">regards,<br>
Richard Morton<br>
On 27 Mar 2013 15:57, "George Nassas" <<a href="mailto:gnassas@mac.com">gnassas@mac.com</a>> wrote:<br>
><br>
> On 2013-03-27, at 7:19 AM, Michael T. Dean wrote:<br>
><br>
> > Well, once we have an embedded DB, you won't "use" MySQL<br>
><br>
> I think the point was why waste machine resources on a duplicate implementation of the rows and columns paradigm?<br>
><br>
> One answer might be that myth is dependant on some arcane feature of mysql and that's fair enough.<br>
><br>
> As a curious question I might also ask if there's going to be a disruptive change why not move to being db-neutral rather than hiding things.</p>
<p dir="ltr">Unfortunately being DBMS neutral is very hard. Each vendor interrupters the SQL standard differently karting to different implementations syntax's and query results.</p>
<p dir="ltr">Some would say this is intentional to cause vendor lock in...</p>
<p dir="ltr">At the moment myth TV rewrites front end devices to connect view a proprietary protocol, an rdbms connection and sometimes via web services and until .24(?) NFS as well.</p>
<p dir="ltr">I would prefer clients to have a single data retrieval method while prevented from making changes to the db which doesn't provide data integrity.</p>
<p dir="ltr">There are many methods for doing this.. The current fashionable choice would be a middle tier of software that is the only thing that connects to the data base and exposes web services for clients to use. </p>
<p dir="ltr">Rich<br><br><br><br></p>
<p dir="ltr">><br>
> - George<br>
><br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</p>