[mythtv-users] mythtv dropping mysql???

[Simon Hobson]

Thomas Mashos <thomas at mashos.com> wrote:

> 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.

OK, now come up with a **practical** method that will handle all the plethora of combinations that people use !
Mine's fairly easy - just one set of tuners, all identical and in one group. Whatever is done needs to support setting the channel numbers of a set of channels based on the callsign, tweaking the callsign on some channels, setting the xmltv id on some, set the EIT flag on some, and set the rest to hidden and shove their numbers up out of the way.
Now consider someone with terrestrial and satellite (eg Freeview and Freesat in the UK) - you now need to handle the channels separately, probably tweaking some more than others (eg to make all the "BBC 1" channels the same).

And then over in the US, from reading here there are users with (for example) multiple tuners, each of which gets a different set of terrestrial channels from multiple transmitters.

Realistically, it going to end up with a scripting language that may or may not look like SQL, but it's going to have a lot of similarities.
Dunno if it's possible to take standard SQL and feed it through to the embedded DB - while restricting the table(s) updated and enforcing things like referential integrity I don't know. But it would go a long way.