#24894: Add CURRENT_TIMESTAMP function to contrib.postgres
----------------------------------+------------------------
Reporter: adamchainz | Owner: adamchainz
Type: New feature | Status: new
Component: contrib.postgres | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------
#24866 implements a Now() function for the ORM. For postgres, it uses
STATEMENT_TIMESTAMP(), in order to be cross-compatible with the other
database backends, rather than CURRENT_TIMESTAMP - this is because
CURRENT_TIMESTAMP is the same across the transaction. Adding a
TransactionNow function to django.contrib.postgres would make this
(default) behaviour discoverable and easily usable with Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/24894>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.16a5a1db50b72f3e7d109ade4fa6ff71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
