comparison README.rst @ 6808:71033bd37b4c

api: change precision of ChangesetStatus.modified_at to seconds Per default MySQL only uses seconds. So in order to be consistent on all databases, this is the easiest solution. I don't think the microseconds are necessary. And AFAICS mercurial only uses seconds for the changeset modification time as well. So why should we use microseconds for ChangesetStatus. Without this, for example test_api_get_changeset_with_reviews fails, because of datetime mismatch if MySQL is used.
author domruf <dominikruf@gmail.com>
date Tue, 08 Aug 2017 21:35:20 +0200
parents 0b6d2ca7175f
children d5eaa70e0f2a
comparison
equal deleted inserted replaced
6807:d43cf470e625 6808:71033bd37b4c