[mythtv] Scheduler needs table keys?
stuarta at squashedfrog.net
Tue Jan 30 09:53:35 UTC 2007
David Engel wrote:
> This would proably work, but I'll need think about it more overnight.
> Part of me would rather add a new value to oldrecorded.duplicate
> instead of a new column. E.g. 2 = current recording, 1 = past
> recording (or never record) and 0 = not recorded or allow re-record.
> Deleting a recording would change or.duplicate to 0 or 1
> appropriately. The scheduler could check for or.duplicate > 0 or > 1
> as specified by the rule.
This makes me wonder whether duplicate is the correct name for the
column, when it clearly is actually the status of the recording.
More information about the mythtv-dev