[Django] #31799: Queryset.update() examine Fields which has auto_now=True

12 views
Skip to first unread message

Django

unread,
Jul 18, 2020, 9:12:32 AM7/18/20
to django-...@googlegroups.com
#31799: Queryset.update() examine Fields which has auto_now=True
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
KimSoungRyoul |
Type: | Status: assigned
Cleanup/optimization |
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I think It is more intuitive to operate like this.

I'd like to ask core contributers for advice.

--
Ticket URL: <https://code.djangoproject.com/ticket/31799>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 18, 2020, 9:12:46 AM7/18/20
to django-...@googlegroups.com
#31799: Queryset.update() examine Fields which has auto_now=True
-------------------------------------+-------------------------------------
Reporter: KimSoungRyoul | Owner:
Type: | KimSoungRyoul
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by KimSoungRyoul):

* owner: nobody => KimSoungRyoul


--
Ticket URL: <https://code.djangoproject.com/ticket/31799#comment:1>

Django

unread,
Jul 20, 2020, 12:41:24 AM7/20/20
to django-...@googlegroups.com
#31799: Queryset.update() examine Fields which has auto_now=True
-------------------------------------+-------------------------------------
Reporter: KimSoungRyoul | Owner:
Type: | KimSoungRyoul
Cleanup/optimization | Status: closed

Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):

* status: assigned => closed
* resolution: => duplicate


Comment:

Duplicate of #15566 with the same proposition that ended with documenting
the current behavior.

--
Ticket URL: <https://code.djangoproject.com/ticket/31799#comment:2>

Reply all
Reply to author
Forward
0 new messages