[Cosmo-dev] Bad ICS already extant

[Randy Letness]

Jared Rhine wrote:
> Thanks for the various commentary about this issue.
>
> >> What can we do about bad data already in the database?
>
> This core issue, "bad data already in the database" seems still open 
> and problematic for migration.
>
> Randy Letness wrote:
>> I added the additional parse check to prevent this, but it shouldn't 
>> effect 0.5 data as that data has already run through parse().
>
> I think 0.5 data is affected in the sense that these broken resources 
> can't be retrieved from a 0.6 instance.  It seems like most dogfooder 
> collections in Cosmo have broken resources, as so to-date, we haven't 
> seen anyone be able to restore a collection from a migrated instance.
>

This shouldn't be an issue for 0.6  migration because all events that 
were created in 0.5 had to be run through ical4j's parser, so there 
should be no bad data in that sense.  The issue only appeared when data 
was being inserted into the db that wasn't run through the parser (0.6 
trunk).

-Randy