Opened 4 years ago

Closed 4 years ago

#12401 closed Bug Report - General (Upstream Bug)

Mythfilldatabase should always grab data for day 0, like it does for day 1

Reported by: JohnLBergqvist@… Owned by: stuartm
Priority: minor Milestone:
Component: MythTV - Mythfilldatabase Version: 0.27-fixes
Severity: low Keywords: mythfilldatabase
Cc: Ticket locked: no

Description

This is dependent on when you actually run mythfilldatabase (i.e. it won't have much effect if you run it at 11PM for example, but it does have an effect if you run it in the early hours of the morning).

Whenever I run mythfilldatabase, it skips over day 0 (the current day) as there is already data in the database, but always grabs program data for the next day (day 1). However this means that you could potentially miss out on very late changes in guide data for the current day, as its relying on guide data that was published one day ago (when today was day 1), rather than published the same day.

For example, Press Association data for the UK, which is used by many UK XMLTV grabbers is updated at approx 05:30AM UK time (https://groups.google.com/forum/#!searchin/atlasapi/time/atlasapi/50s4Ea-3Few/iGZkjaRPBhUJ), and so I schedule my Mythfilldatabase to run at 6:00 daily, however because it's skipping over day 0, the data for that day is always 1 day old unless I manually over-ride it.

So if we're Always grabbing data for day 1 (as it's closest), shouldn't we grab data for day 0 as well?

Change History (1)

comment:1 Changed 4 years ago by stuartm

Resolution: Upstream Bug
Status: newclosed

For XMLTV the behaviour is chosen by the grabber, not mythtv

Note: See TracTickets for help on using tickets.