#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):
I think the choice to keep `Now()` consistent was the right one.
Milliseconds might not seem like much, but the distinction between
"multiple objects created in one transaction have identical timestamp" vs
"multiple objects created in one transaction have very slightly different
timestamps" is a crucial difference in some cases, like if you're trying
to enforce unique timestamps, or trying to later query objects that were
created together, or whatever. I think potentially-critical semantic
differences like that should be reflected in the code, and we should avoid
making them inconsistent between database backends when possible.
As far as I'm concerned, a cross-db-consistent `Now()` plus a
`TransactionNow()` in `contrib.postgres` is pretty much the ideal
resolution here.
--
Ticket URL: <https://code.djangoproject.com/ticket/24894#comment:3>
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.2875ff0084060cec540454e84ff1fdac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
