Closed
Bug 504236
Opened 16 years ago
Closed 16 years ago
Allow separate weave and storage versions
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
0.5
People
(Reporter: Mardak, Assigned: Mardak)
Details
We set both versions to whatever the weave version is. This can cause unnecessary server wipes on updates that don't actually change record formats.
Assignee | ||
Comment 1•16 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/fb1fa1f09a67
Update the substitution names to separately replace the storage version with the new storage version Makefile variable.
Assignee: nobody → edilee
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.5
Assignee | ||
Comment 2•16 years ago
|
||
thunder: Should we bump storage_version to 0.5pre2 because bug 479189 introduces a new record type.. BookmarkQuery for place: queries. Right now they get synced as Bookmark, so a wipe is needed to make sure they get uploaded with the right type.
But then again how many people have smart tags folders?
Comment 3•16 years ago
|
||
(In reply to comment #2)
> thunder: Should we bump storage_version to 0.5pre2 because bug 479189
> introduces a new record type.. BookmarkQuery for place: queries. Right now they
> get synced as Bookmark, so a wipe is needed to make sure they get uploaded with
> the right type.
>
> But then again how many people have smart tags folders?
The local metadata wipe should take care of fixing the broken records. So long as we can read the 0.5pre1 server format, we should not bump the min storage version.
Updated•6 years ago
|
Component: Firefox Sync: Build → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•