Re: [Django] #26296: values() after extra() gives incorrect error message

2016-03-11 Thread Django 
#26296: values() after extra() gives incorrect error message
-+-
 Reporter:  vvkuznetsov  |Owner:
 Type:   |  vvkuznetsov
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 The patch causes a regression in another unit test, so I'm not going to
 bother spending more time on this.

--
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/069.43e8b21db707909b60a24b9bac9b0a02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26296: values() after extra() gives incorrect error message

2016-03-02 Thread Django 
#26296: values() after extra() gives incorrect error message
-+-
 Reporter:  vvkuznetsov  |Owner:
 Type:   |  vvkuznetsov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  db =>
 * component:  Documentation => Database layer (models, ORM)
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I guess the patch is simple enough. It just needs a test.

--
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/069.1ef756ae5e3a17d1c0f24ac14c8fb28a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26296: values() after extra() gives incorrect error message (was: Trick with extra fields)

2016-02-29 Thread Django 
#26296: values() after extra() gives incorrect error message
-+-
 Reporter:  vvkuznetsov  |Owner:
 Type:   |  vvkuznetsov
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  db   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 Note [https://docs.djangoproject.com/en/dev/ref/models/querysets/#extra
 the documentation], "This is an old API that we aim to deprecate at some
 point in the future. Use it only if you cannot express your query using
 other queryset methods. If you do need to use it, please file a ticket
 using the QuerySet.extra keyword with your use case (please check the list
 of existing tickets first) so that we can enhance the QuerySet API to
 allow removing extra(). We are no longer improving or fixing bugs for this
 method."

 In light of that, is it worth fixing this?

--
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/069.d54ff979217d6f93aebdcaf6d719e0ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.