As I said, the current code has bug if time precision is lost when saving
in db. You had better switch to other version type (e.g. long type). Not
sure the bug is worthwhile to fix, though.