Closed Bug 503964 Opened 13 years ago Closed 12 years ago

Have per-engine versioning to avoid wiping all engine data

Categories

(Firefox :: Sync, defect, P2)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

Attachments

(1 file, 1 obsolete file)

Right now we have a single "data version" that we need to bump if formats for any engine record changes. We can put in a version field in the base engine class that detects when there's conflicts and wipe data first.

Alternatively, we store an array of versions in the meta/global as we're fetching that anyway.
Priority: -- → P2
Target Milestone: --- → 1.0
Assignee: nobody → edilee
Flags: blocking-weave1.1+
Target Milestone: 1.0 → 1.1
Target Milestone: 1.1 → 1.2
Depends on: 554472
Attached patch v1 (obsolete) — Splinter Review
Attachment #434388 - Flags: review?(mconnor)
Attached patch v1.1Splinter Review
Fixed a typo
Attachment #434388 - Attachment is obsolete: true
Attachment #434391 - Flags: review?(mconnor)
Attachment #434388 - Flags: review?(mconnor)
Attachment #434391 - Flags: review?(mconnor) → review+
Whiteboard: [has patch][has review]
http://hg.mozilla.org/labs/weave/rev/7b28228b1692
Add an engines object to meta/global to track version and syncID for each engine. If the server is outdated, wipe the data and set a new version and syncID. If the client is oudated, ask for an upgrade. Differing syncIDs cause a reupload. All engines are right now the default version 1.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [has patch][has review]
Blocks: 549635
Depends on: 545517
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.