[mythtv-users] mythtv dropping mysql???

[Thomas Mashos]

On Thu, Oct 16, 2014 at 12:37 PM, Simon Hobson <linux at thehobsons.co.uk> wrote:
> Thomas Mashos <thomas at mashos.com> wrote:
>
>> That's just it though, when you take it internal you don't need to
>> consider different use cases as the only use case for the DB is
>> MythTV. The only considerations you need to take into account are
>> hardware.
>
> I'm also talking about "appliances" where the only DB use is MythTV. But I'm not talking about use cases as in how many DBs you run, but how someone uses the Myth system. If you can tune an internal DB "just like that" for all use cases then you can also programatically tune an external DB - the process is the same regardless of whether it's internal or external.
>
> Just think of all the variables :
> Number and type of tuners for starters, then the number and type of channels, volume of recording rules, volume of recordings and previously recorded.
> Then frontends.
> And schedule grabbers which have variable demands on the DB.
>
> But ultimately it's for the devs to decide.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

While that is true, it's pretty bad form to automatically tune a DB
for MythTV if MythTV isn't the only thing using it.

-- 
Thanks,

Thomas Mashos