#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
----------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Carl says:
I find `TransactionNow()` to be more useful than `Now()` in most cases I
run into (e.g. it's often useful for two objects created in the same
transaction to have the same creation timestamp). In other words, as usual
Postgres gets it right and the other databases get it wrong :-)
[[BR]][[BR]]
That said, `TransactionNow()` (like any other SQL function) is now
trivial to implement yourself, so I won't be bothered if it doesn't make
it into contrib.postgres. But on balance I'd be in favor.
Other opinions?
--
Ticket URL: <https://code.djangoproject.com/ticket/24894#comment:1>
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.0f5364177b2d18d6d2c5924dd05c8809%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
