[mythtv-users] mythtv dropping mysql???

[Thomas Mashos]

On Wed, Oct 22, 2014 at 12:16 PM, Simon Hobson <linux at thehobsons.co.uk> wrote:
> Rich Freeman <r-mythtv at thefreemanclan.net> wrote:
>
>> I do realize that some of this might
>> be doable via scripting, but unless the script just runs raw SQL on
>> the database you're not going to get the same performance out of it
>> and it is another "language" to learn.  If it does run raw SQL on the
>> database, then there is no way to control it and you get all the
>> downsides of allowing outside database access today.
>
> Not quite. Even if they accepted raw SQL and ran it against the DB - they still get to control access in as much as nothing can be accessing the DB without going through the backend. That makes (as has been pointed out) several tasks easier/safer.
>
>
>
> Thomas Mashos <thomas at mashos.com> wrote:
>
>> Completely separate from the topic, I've got to ask. Why are you guys
>> doing so much work on your MythTV install? What I mean is, what are
>> you accomplishing with this?
>
> I don't do a huge amount, but a key task for me is editing the channels table.
> Here in the UK, on Freeview, the default (logical) channel numbers are crap. As far as I can tell, it's a case of the original 5 analogue channels got LCNs 1-5, then the rest seem to have been given arbitrary numbers as they came up. Now that's one thing I can't stand.
> So, no problem to just pop up the channel editor (in MythWeb) and change them. I can also enter the XMLTV IDs at the same time.
> That's OK ... once.
>
> Then when we have to rescan because they've had yet another shuffle, you have to do it all again.
>
> So I have a SQL script (it's in the Wiki) that hides all the crap (shopping channels etc), sets channel numbers as I want them, sets the XMLTV IDs (or sets the EIT flag).
>
> Whatever we get needs to be scriptable - a "point and click" UI is a complete waste of time for most of the use cases people are giving.
>
> _______________________________________________
> 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 I agree with the problem, couldn't that be resolved by some
initial config then sanitation of the input from the scan process? I'm
just wondering if it makes more sense to fight the problem as far up
the chain as we can (in this case, before the data gets into the DB)
than the symptom. I think I've heard similar issues with people fixing
channel and/or epg data before and it just seems to me that if we did
some sanitation of data when it's input in the DB, there wouldn't be a
need to fix it in the DB.

-- 
Thanks,

Thomas Mashos