[mythtv] conflict resolution

Isaac Richards ijr at po.cwru.edu
Mon Nov 3 00:12:17 EST 2003


On Sunday 02 November 2003 09:26 pm, David Engel wrote:
> On Sun, Nov 02, 2003 at 04:59:46PM -0600, David Engel wrote:
> > > How would override record (1) compare with
> > > single record (record.type == 1)? Have you considered adding
> > > a new type for the 'record' table for "don't record" rather
> > > than adding a new table with essentially the same fields?
> >
> > I haven't really given such an approach much consideration.  My gut
> > feel is that it would be more complicated.
>
> I've now given this some thought and believe the main difference is
> this.  The recordoverride approach more easily lends itself (as I
> intended) to keeping the overrides associated with the original record
> entry.  So, for example, if the record entry is deleted, the overrides
> get deleted too.  The new single record/don't record approach lends
> itself to disassociating the override from the "mother" record entry,
> so the overrides would remain if the original record entry was
> deleted.
>
> So I think it boils down to which behavior is desirable that
> determines which approach to take.  I see benefits for each.  At this
> point, it's up to Isaac.  I just want to know which way to go, since
> I've wanted this feature for quite a while and have the time and
> motivation to work on it right now.

I don't really have a preference between the two approaches -- I'm pretty 
content with things as they work now.  

I think that since you're actually taking the time to implement it, you should 
pick =)

Isaac



More information about the mythtv-dev mailing list