django1/django/db/backends
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
..
base Used time.monotonic() instead of time.time() where applicable. 2019-05-08 18:34:22 +02:00
dummy Made DatabaseFeatures.uses_savepoints default to True. 2018-10-25 10:02:47 -04:00
mysql Refs #30380 -- Used cursor._executed in DatabaseOperations.last_executed_query() on MySQL. 2019-04-21 12:17:05 +02:00
oracle Fixed #30408 -- Fixed crash when adding check constraints with LIKE operator on Oracle and PostgreSQL. 2019-04-30 07:38:22 +02:00
postgresql Fixed #30408 -- Fixed crash when adding check constraints with LIKE operator on Oracle and PostgreSQL. 2019-04-30 07:38:22 +02:00
sqlite3 Removed unnecessary assignments in various code. 2019-04-24 13:09:29 +02:00
__init__.py Fixed #22603 -- Reorganized classes in django.db.backends. 2015-01-14 14:16:20 -05:00
ddl_references.py Fixed #28077 -- Added support for PostgreSQL opclasses in Index. 2018-06-29 17:00:28 -04:00
signals.py Fixed #13798 -- Added connection argument to the connection_created signal. Thanks to liangent for the report, and Alex Gaynor for the patch. 2010-08-30 13:21:18 +00:00
utils.py Used time.monotonic() instead of time.time() where applicable. 2019-05-08 18:34:22 +02:00