#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 | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by carljm):
One other thought - I would like to see this patch include some kind of
brief note in the `Now()` docs to alert Postgres users (who may be
accustomed to Postgres' `CURRENT_TIMESTAMP` behavior) that `Now()` is the
_statement_ timestamp on all databases, and direct them to
`TransactionNow()` if that's what they want.
--
Ticket URL: <https://code.djangoproject.com/ticket/24894#comment:4>
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/068.70ae5651d2868d7a92e8225c1c77687b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
