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
..
__init__.py	Fixed #22603 -- Reorganized classes in django.db.backends.	2015-01-14 14:16:20 -05:00
base.py	Used time.monotonic() instead of time.time() where applicable.	2019-05-08 18:34:22 +02:00
client.py	Refs #27656 -- Updated django.db docstring verbs according to PEP 257.	2017-02-28 09:17:27 -05:00
creation.py	Fixed #30184 -- Removed ellipsis characters from shell output strings.	2019-02-13 13:59:44 -05:00
features.py	Refs #30172 -- Prevented removing a field's check or unique constraint from removing Meta constraints.	2019-03-17 20:50:22 -04:00
introspection.py	Fixed #29949 -- Refactored db introspection identifier converters.	2018-11-21 09:06:50 +01:00
operations.py	Fixed typos in docs, comments, and exception messages.	2019-04-18 09:33:53 +02:00
schema.py	Fixed #30444 -- Moved SQL generation for tables to BaseDatabaseSchemaEditor.table_sql().	2019-05-07 10:28:14 +02:00
validation.py	Refs #27859 -- Refactored BaseDatabaseValidation to use check_field_type().	2017-05-14 18:34:45 +02:00