[Cosmo-dev] bug: 7127 move ContentItem.content and content*
properties to table fields
twl at osafoundation.org
Thu Oct 19 14:39:41 PDT 2006
So over in Chandler, there have been lots of schema changes. It was
only fairly recently that Chandler could detect that the schema of
the local store had changed. Before that, we had a practice of
sending a note to the dev list letting people know that the schema
Would this be a worthwhile practice for us to adopt? I know that
all the committers are reading every commit message, but there are
folks on this list who might be impacted by such changes, and who may
not be reading the commit logs...
On Oct 19, 2006, at 12:53 PM, Randy Letness wrote:
> Jared Rhine wrote:
>> Please confirm: this patch is a schema change and thus running
>> of Cosmo 0.5-SNAPSHOT should wipe their databases. It goes
>> without saying
>> that people running 0.5-SNAPSHOT are on their own and can only
>> expect schema
>> stability/migration support in released versions.
>> I'm likely to upgrade osaf.us to an svn release prior to r2703,
>> the r2703 data wipe to avoid stomping on the testing we've asked
>> people to do.
> Yes the fix required a schema change, and older versions of 0.5-
> will require a new db. This should be the last of the schema changes
> for 0.5.
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev