[mythtv-users] inconsistent inetref in recorded table

[Frank Phillips]

On Sun, Jan 24, 2016 at 7:54 AM, Brian J. Murrell <brian at interlinx.bc.ca>
wrote:

> On Sun, 2016-01-24 at 06:11 +0100, Hika van den Hoven wrote:
>


> <snip>
>


>
> >
> > The one jumping to tmdb3.py is probably because of missing episode
> > info!
>
> Yes.  That episode has the generic show data.  But that doesn't explain
> how it got a TMDB ID of 15714.  According to my (next to zero)
> knowledge of TMDB, 15714 is "Seaside Special" (https://www.themoviedb.o
> rg/tv/15714).
>
> But even that only answers half of the question.  Of the remaining
> entries why are some 75710 and others ttvdb.py_75710?  Given that the
> difference correlates to time, it seems that the format of the field
> was changed to include which scraper the ID is for.
>
> But then why didn't the database migration for whichever version that
> introduced that change update the existing inetrefs rather than leaving
> them inconsistent like this?
>
> >  I don't know the precise algorithm to determine which to use,
> > but that is part of it.
>
> If I had to guess it's based on an ordered list and the first one to
> return info wins.  ttvdb is probably higher in the list than tmdb3.
>
> Cheers,
> b.
>
>
This is where the TMDB grabber was looking, the only movie result from a
'Criminal Minds' search:
https://www.themoviedb.org/movie/15714-like-minds

The grabber name started being prepended with 0.27.4. Some tips to get them
straight:
http://www.gossamer-threads.com/lists/mythtv/users/585371#585371
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160125/d434d7b3/attachment.html>