U1DB Qt/ QML

putDoc should optionally take a revision

Bug #1276680 reported by Cris Dywan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
U1DB Qt/ QML
Triaged
High
Unassigned
U1DB Qt/ QML 2.0

Bug Description

Right now using putDoc to add a document with an existing docId will fail, so it can be used only to add new documents unless they are manually deleted first. For reliable sync behavior the API needs to take an optional known revision to make a decision to replace it if it's newer.

Tags: sync
Revision history for this message
Stuart Langridge (sil) wrote :

See https://one.ubuntu.com/developer/data/u1db/conflicts for relevant discussion of how revisions need to work.

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

Moving to U1DB-QT Milestone 2.0 to first focus on issues related to querying and filtering. Sync with U1 is a feature we can come to at a later point.

Changed in u1db-qt:
milestone: none → 2.0
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.