On 02/14/2011 03:52 PM, Sascha Silbe wrote:
Excerpts from Simon Schampijer's message of Mon Feb 14 21:01:18 +0100 2011:
So if the timestamp is missing we will create the entry with the current
timestamp when we update_the_index. I guess there is no better timestamp
we can set.
Exactly. I
Excerpts from Simon Schampijer's message of Tue Feb 15 17:11:22 +0100 2011:
Hmm, where does the ctime property actually comes from, is it a property
of the old DS?
Exactly.
I think just doing the check as you have it and setting
update_metadata to true should be enough.
Good. I'll send
On 02/11/2011 07:50 AM, Sascha Silbe wrote:
The timestamp property might be missing due to incomplete writes (out of
power, system crash) or software bugs.
So if the timestamp is missing we will create the entry with the current
timestamp when we update_the_index. I guess there is no better
Excerpts from Simon Schampijer's message of Mon Feb 14 21:01:18 +0100 2011:
So if the timestamp is missing we will create the entry with the current
timestamp when we update_the_index. I guess there is no better timestamp
we can set.
Exactly. I considered setting it to 0 instead, but the
The timestamp property might be missing due to incomplete writes (out of
power, system crash) or software bugs.
Signed-off-by: Sascha Silbe si...@activitycentral.com
---
src/carquinyol/datastore.py |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git
5 matches
Mail list logo
