Przemysław Suliga af5ec222cc Used time.monotonic() instead of time.time() where applicable. ... time.monotonic() available from Python 3.3: - Nicely communicates a narrow intent of "get a local system monotonic clock time" instead of possible "get a not necessarily accurate Unix time stamp because it needs to be communicated to outside of this process/machine" when time.time() is used. - Its result isn't affected by the system clock updates. There are two classes of time.time() uses changed to time.monotonic() by this change: - measuring time taken to run some code. - setting and checking a "close_at" threshold for for persistent db connections (django/db/backends/base/base.py).		2019-05-08 18:34:22 +02:00
..
examples
aggregation.txt	Fixed #30347 -- Fixed typo in docs/topics/db/aggregation.txt.	2019-04-13 12:35:31 +02:00
index.txt
instrumentation.txt	Used time.monotonic() instead of time.time() where applicable.	2019-05-08 18:34:22 +02:00
managers.txt
models.txt
multi-db.txt
optimization.txt
queries.txt	Fixed #30365 -- Fixed syntax highlighting in SQL examples.	2019-04-23 12:37:50 +02:00
search.txt
sql.txt
tablespaces.txt
transactions.txt