Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"421ad283d3a0c9814e6cf5b87b393dce09f59474" 421ad283]:
 {{{
 #!CommitTicketReference repository=""
 revision="421ad283d3a0c9814e6cf5b87b393dce09f59474"
 [1.9.x] Fixed #26239 -- Added a note about how auto_now works with
 QuerySet.update().

 Backport of ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2 from master
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a04fd6a2050f1ed44feb7ab1c9830f93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2" ca5c05d]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2"
 Fixed #26239 -- Added a note about how auto_now works with
 QuerySet.update().
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.acedb11dd39f8eec9dc24cc2ae290fc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by duane9):

 Okay, I added a note to that effect.
 https://github.com/django/django/pull/6281

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c5992bce0cdedf03fbc515aff777da5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 How about adding something like, "The field is not updated when using
 `QuerySet.update()` to update other fields."

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.84827ae70cca0e6d2d2f3a2519eff110%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by boussouira):

 I think that is good enough.
 Thank you
 > [comment:6 duane9]:
 > I think the documentation already specifies this: "Automatically set the
 field to now every time the object is saved."
 >
 
https://docs.djangoproject.com/en/1.9/ref/models/fields/#django.db.models.DateField.auto_now
 >
 > Does the documentation need something more?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.1729e4310822ceaf1ab2d8c4d093b149%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by duane9):

 Replying to [comment:4 boussouira]:
 I think the documentation already specifies this: "Automatically set the
 field to now every time the object is saved."
 
https://docs.djangoproject.com/en/1.9/ref/models/fields/#django.db.models.DateField.auto_now

 Does the documentation need something more?

 > Hi, Sorry for delay in replay.
 > I think documentation change is better, so existing applications won't
 have to do any changes to upgrade.
 > As i understand now, you must call `save()` for the auto-update field to
 be populated, which is fine, but explicitly mentioning that in the
 documentation good for new users (like me).
 > Thank you.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2084190469d89103af6860150a4eff5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by duane9):

 * status:  new => assigned
 * owner:  nobody => duane9


--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a578e2a7bbf7411e05012a45e2445f65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by boussouira):

 Hi, Sorry for delay in replay.
 I think documentation change is better, so existing applications won't
 have to do any changes to upgrade.
 As i understand now, you must call `save()` for the auto-update field to
 be populated, which is fine, but explicitly mentioning that in the
 documentation good for new users (like me).
 Thank you.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d1e855be00654e2b21cbaee2b25d5012%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by honsdomi):

 Replying to [comment:2 AMaini503]:
 > Replying to [ticket:26239 boussouira]:
 > > I don't know if this is a bug or not, but when using `update()`, the
 DateTime fields with `auto_now` are not updated to the current time. The
 documentation of `auto_now` doesn't say anything about that situation.
 > > For example:
 > >
 > > {{{
 > > #  This won't update `updated_at`:
 > > Order.objects.filter(user_id=7).update(check_count=3)
 > >
 > > # You have to explicitly include it in update()
 > > Order.objects.filter(user_id=7).update(check_count=3,
 updated_at=timezone.now())
 > > }}}
 >
 > --> I will try to work on this. But should update be modified to include
 timestamp by itself or documentation should be altered to state that
 timestamp needs to be passed explicitly ?

 Hello, can someone confirm if this requires modifying code or just
 documentation?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.dc10056f6ce6c9d00b21738574e14aeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by AMaini503):

 Replying to [ticket:26239 boussouira]:
 > I don't know if this is a bug or not, but when using `update()`, the
 DateTime fields with `auto_now` are not updated to the current time. The
 documentation of `auto_now` doesn't say anything about that situation.
 > For example:
 >
 > {{{
 > #  This won't update `updated_at`:
 > Order.objects.filter(user_id=7).update(check_count=3)
 >
 > # You have to explicitly include it in update()
 > Order.objects.filter(user_id=7).update(check_count=3,
 updated_at=timezone.now())
 > }}}

 --> I will try to work on this. But should update be modified to include
 timestamp by itself or documentation should be altered to state that
 timestamp needs to be passed explicitly ?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2d95e7a7fee0f03398034f362e6e3f2e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.1779e3e0c8cf6242c215bd8b0b294578%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
---+
 Reporter:  boussouira |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I don't know if this is a bug or not, but when using `update()`, the
 DateTime fields with `auto_now` are not updated to the current time. The
 documentation of `auto_now` doesn't say anything about that situation.
 For example:

 {{{
 #  This won't update `updated_at`:
 Order.objects.filter(user_id=7).update(check_count=3)

 # You have to explicitly include it in update()
 Order.objects.filter(user_id=7).update(check_count=3,
 updated_at=timezone.now())
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.47ae7ca09954bfc936780b90e5d284da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.