nickfelt bc02b701b5 Use transaction time when cloneProjectedAtTime()-ing within transaction ... It's bad practice in terms of data model consistency to use DateTime.now(UTC) for cloneProjectedAtTime() within a transactional context - instead, we should always use ofy().getTransactionTime() when it's available. The ofy transaction time is frozen at the start of the transaction attempt, whereas DateTime.now(UTC) will continue marching ahead. So using it for a cloneProjectedAtTime() could mean materializing the outcome of logical-time-dependent events (like autorenews, or transfers, or grace period expirations) at a logical time (i.e. commit log time) prior to when they should actually have occurred. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=170501277		2017-10-04 16:16:45 -04:00
..
com/google/testing/builddefs	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
google/registry	Use transaction time when cloneProjectedAtTime()-ing within transaction	2017-10-04 16:16:45 -04:00