[Cosmo-dev] Recurrence modifications, filters, and diffs

[Randy Letness]

Brian Moseley wrote:
>
> what would be the impact of making things that are now columns be
> Attributes instead?
> .

It would mean a lot of refactoring and a performance hit due to the 
extra rows, joins involved.  What attributes are we talking about 
anyway?  Is "reminderTime" the main example?

> we'd have to have model layer validation for mandatory attributes -
> which we might already have to some extent.

Right, which we are doing in some cases already.

> we'd obviously have a bunch of refactoring.
>
> what else?
>

It would add a lot of migration work.

> jeffrey suggested using a marker value to indicate missing. this would
> have to be a value that nobody would realistically use.
>

Yeah but we would have to handle different data types (string, number, 
timestamp, etc), so we would have to define a unique value for each type 
and all code using this attribute would have to be aware of these marker 
values.

> theoretically i like the idea of making everything an Attribute, but
> i'm suspicious of the amount of work involved.  

Yeah its a lot of work. 

-Randy