[mythtv] Why MythTV didn't handle the UK Freeview lineup change

[Rob Smith]

On Sun, Jul 26, 2009 at 10:23 AM, John Barberio<barberio at lineone.net> wrote:
> I don't see much leway for 'user error' here. The 'deleted channel' kept
> getting recreated, until mythfilldatabase was run after the delete
> operation. And it looks very much like a 'dirty cache' problem to me. There
> may well be some user setting in the mysql server on my end that causes the
> table to be cached, that doesn't happen on yours. It may be that this bug
> only gets exposed with mysql servers set up in a specific way. But it's
> still a bug seen by two different people, who could work-around it the same
> way with the same results, and with the same very simple fix of ensuring the
> database consistency when doing a scan, and perhaps offering a 'delete all
> channels and rescan' option to assist for future lineup changes.
>
> Generally, any programer should be wary of declaring 'it just does not work
> that way'. Perhaps you meant 'it should not work that way', since apparently
> it has. As an aside, this very much reminds me of the Source Engine stutter
> bug which 'just does not work that way', fixed only after they realised
> their QA test boxes were all vanilla XP, and none had 'Asian Language
> Support' enabled.

The only 'cache' here is the memory cache the backend has, which is
why when you start myth-setup, it tells you that you need to shutdown
all backends while it's doing it's thing. That said, there is no cache
that the mysql server would have in this case that would prevent your
table changes from taking effect.

*If* you actually believe this is the issue, why don't you prove it?
Run a query on the database, see the channels, wipe them from the
database with mythtv-setup, re-run the query and show that they're
still there, then run mfdb and then show them gone. That's the steps
we'd need to show that it's something epic odd rather then just user
error with not shutting down all the backends as requested or the
like.

And all you're currently doing is making the entire development team
upset with you when you're not giving us any hard information on your
bug and basically telling us off while demanding help, and telling us
(including those of us who are successful career developers) that
we're doing things wrong, which certainly isn't making you any
friends...

My vote at this point is, unless you start giving us hard information,
to drop this thread now and if it's not dropped, to remove access to
the list.

~Rob