diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-05-11 18:22:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-11 18:22:55 +0200 |
| commit | 72a86ceb33749d4fd17d3d2910e19b9d9ca1643b (patch) | |
| tree | 8cc73d35de117ae7e9239de71923d77221acf631 /docs/ref | |
| parent | 2b11740e1d9d23ef53d94a1c45896fb7b91df908 (diff) | |
Fixed #34558 -- Fixed QuerySet.bulk_create() crash with Now() on Oracle.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/database-functions.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/ref/models/database-functions.txt b/docs/ref/models/database-functions.txt index 13b70d76cd..f22a7ae386 100644 --- a/docs/ref/models/database-functions.txt +++ b/docs/ref/models/database-functions.txt @@ -562,11 +562,21 @@ Usage example: ``Now()`` uses ``STATEMENT_TIMESTAMP`` instead. If you need the transaction timestamp, use :class:`django.contrib.postgres.functions.TransactionNow`. +.. admonition:: Oracle + + On Oracle, the SQL ``LOCALTIMESTAMP`` is used to avoid issues with casting + ``CURRENT_TIMESTAMP`` to ``DateTimeField``. + .. versionchanged:: 4.2 Support for microsecond precision on MySQL and millisecond precision on SQLite were added. +.. versionchanged:: 5.0 + + In older versions, the SQL ``CURRENT_TIMESTAMP`` was used on Oracle instead + of ``LOCALTIMESTAMP``. + ``Trunc`` --------- |