Closed Bug 708005 Opened 14 years ago Closed 14 years ago

Ensure safe handling of history truncation

Categories

(Firefox for Android Graveyard :: Android Sync, defect, P1)

Product:
Firefox for Android Graveyard
Component:
Android Sync
Type:
defect

Tracking

(fennec+)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
fennec + ---

People

(Reporter: rnewman, Unassigned)

References

Details

Both the Android global store and Fennec truncate history (to 250 items, I believe). In a reset sync scenario, we might insert many more than that. We need to ensure that: * We don't fetch and apply more records than the local DB will care about * We don't lose upstream history because of local truncation * In the course of normal sync * In a merge-reset
tracking-fennec: --- → ?
tracking-fennec: ? → +
Depends on: 721898
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.