Putting and then getting dates in a document are altered by u1db

Bug #1482503 reported by Didier Roche-Tolomelli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
u1db-qt (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When putting and getting a QML date in the u1db database, the resulting strings are stored differently, even if you don't do any type conversion.

The result is that the resulting date is shifted by the current timezone, rendering an incorrect date.

Small example:

date is "Sun Jul 5 17:20:46 2015 GMT+0200"

This value is jsonified in var current = {"title":"First element","date":"2015-07-05T15:20:46.000Z"}

console.log("Before save: " + JSON.stringify(tosave));
db.putDoc(tosave, current.billId);
var after = db.getDoc(current.billId.toString())
console.log("After save: " + JSON.stringify(afterSave));

log is:
qml: Before save: {"title":"First element","date":"2015-07-05T15:20:46.000Z"}
qml: After save: {"date":"2015-07-05T17:20:46","title":"First element"}

-> Note that the date element has been altered and isn't returned in the same format The date should be returned unalterned.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

launchpad seems to continue to report bug twice when clicking on submit, invalidating.

Changed in u1db-qt (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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