[mythtv-users] Slow MySQL query after delete

Michael T. Dean mtdean at thirdcontact.com
Wed Sep 5 17:51:41 UTC 2007

On 09/05/2007 01:13 PM, Mike Perkins wrote:
> Jay R. Ashworth wrote:
>> So that my point (from another part of the thread) is clear:
>> I can live with them not ever making it possibel to run atop PgSQL.
> In fact, localising the database access into one component should make it easier 
> to run atop whatever database you wish, since you should be able to just replace 
> the MySQL component with something else. Assuming the devs put enough thought 
> into arranging the interface API between the db component and everything else so 
> that it's reasonably db-neutral, of course.
> Since the database would be hidden by the component, it wouldn't make any 
> difference (to the application) if the db was embedded, separate, MySQL, or 
> anything else.
> (Just needs someone to code it, of course ;)

And keep up with it.  I think it's a given that MythTV does /not/
promise a stable binary API.  :)

But your point is valid--if someone really cares, he/she is welcome to
code a replacement.


More information about the mythtv-users mailing list