Opened 18 years ago
Closed 18 years ago
#2207 closed patch (fixed)
mythfilldatabase does not update status info to DB when run in eitonly mode
Reported by: | otto at kolsi dot fi | Owned by: | Stuart Auchterlonie |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | mythtv | Version: | head |
Severity: | low | Keywords: | |
Cc: | Ticket locked: | no |
Description
mythfilldatabase does not update values 'mythfilldatabaseLastRunStart' and 'mythfilldatabaseLastRunEnd' to DB, when it is run only for EIT data. 'mythfilldatabaseLastRunStatus' also get's always a warning messsage about possible problems although it shouldn't (eitonly does not add anything to program table).
Attached patch contains one solution for these issues. It modifies mythfilldatabase to update LastRunStart? and LastRunEnd? values (with same timestamp). Also if we are in eitonly -mode, LastRunStatus? get's proper message.
These changes fix the mythfilldatabase status info in frontend and in mythweb when only EIT data is used.
Attachments (2)
Change History (4)
Changed 18 years ago by
Attachment: | mythfilldb-eit.diff added |
---|
Changed 18 years ago by
Attachment: | mythfilldb-externally_handled.diff added |
---|
comment:1 Changed 18 years ago by
Owner: | changed from Isaac Richards to Stuart Auchterlonie |
---|
Updated patch from Michael T. Dean. Works now for mixed sources (eitonly and non-eitonly) and also for no_grabber sources.