[dev] iCalendar stuff

[Chuck Hagenbuch]

Quoting Karsten Fourmont <fourmont at gmx.de>:

> I've got 3 ideas, none seem to completly solve the problem:
>
> 1) add new "uid" field to table kronolith_events
> 2) store uid in datatree
> 3) try to use external UID as primary key if possible. If not, to some
> clever fallback to what?? 2)??

I'd say 1.

> 1) works only with our mysql backend. Not good.

Not true - it'd work fine with the search patch that's been submitted, 
since you
can already store arbitrary attributes in MCAL. And I'm sure we can add an
extra attribute to the iCal data that the kolab backend stores.

-chuck

--
"Regard my poor demoralized mule!" - Juan Valdez