[mythtv-users] Schedules Direct TBA Listings

[Mike Perkins]

On 23/07/14 19:12, R. G. Newbury wrote:
> On 18/07/14 04:55 PM, Gary Buhrmaster wrote:
>> On Fri, Jul 18, 2014 at 8:13 PM, Michael T. Dean
>> <mtdean at thirdcontact.com> wrote:
>>> On 07/18/2014 04:00 PM, R. G. Newbury wrote:
>>>> I am interested in understanding why you think the JSON grabber 'overloads'
>>>> the mythconverg database.
>>
>> ....
>>
>>> I think he's talking about the fact that it adds tables that are only useful
>>> to the Schedules Direct JSON grabber
>
>> To be honest, MythTV itself does not follow all the
>> "recommendations"/"rules" either, but at least it
>> is all MythTV.  But for something so clearly outside
>> of MythTV itself (a SD JSON grabber should ideally
>> be able to be used in alternative XMLTV apps that
>> do not have MythTV installed at all), this would
>> logically be completely independent of the
>> mythconverg database.
>
> If that is the operative philosophy, then mythfilldatabase should not write to
> mythconverg either. It too is a actually a standalone grabber. It just happens
> to be the first one written to talk to Zap2it/Tribune etc. and so it was/is
> included in the myth package.
>
> True, it would to a certain extent be more "elegant" if mfdb and mfdb-json wrote
> to their own database, but you *still* have to chunk the data into
> mythconverg... which would involve opening two databases copying tables from one
> to the other.
>
> I think that is called 'make-work'.
>
> It would be nice if mfdb-json could also/instead write to a standalone mysql db,
> which other player programs can use. I suspect that that would not be too
> difficult to create.. it would amount to a mythconverg with the
> playback/music/gallery etc tables never created.
>
> An advantage of having mfdb and mfdb-json writing to mythconverg is that they
> make efficient use of the existing infrastructure, and only add tables which are
> necessary to the conversion process of taking the raw download and making it
> properly accessible to myth. And any other grabber could do the same.
>
> Geoff
>
...for values of "I use Schedules Direct."

For everybody else on the planet who uses mythtv, mythfilldatabase takes an 
xmltv feed and converts it into the format myth requires and then updates the 
database accordingly.

For those people (like myself), the Schedules Direct method of operation looks 
like an outlier. All the run options to mythfilldatabase which concern SD are 
meaningless to us.

I'd prefer the mythconverg database to remain clean and only concerned with its 
prime function, that of controlling the scheduling, recording and managing 
recorded shows. To that end I've never been a fan of the plugins which add their 
own tables, often conflicting with myth's own, into mythconverg. They ought to 
be in separate databases, and that goes for all EPG feeds.

-- 

Mike Perkins