Re: [Django] #27982: Possible bug related to queryset union

2017-07-14 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by gigelu):

 Yes, after I've added `or self.combinator` in the if clause, it does a
 `SELECT COUNT (*) FROM (... old query ...)`,  so the result is good 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/064.a46a2b91e1ddd5430884d59df1ca8ac1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27982: Possible bug related to queryset union

2017-07-14 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Apolloner):

 @gigelu: Can you check if https://github.com/django/django/pull/8769 fixes
 the issue?

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

Re: [Django] #27982: Possible bug related to queryset union

2017-03-29 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by gigelu):

 Maybe if you catch the exception here
 https://github.com/django/django/blob/master/django/core/paginator.py#L73
 too so the pagination will continue to work, otherwise it will be pretty
 confusing (I want to paginate some queryset and I get a count error).

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

Re: [Django] #27982: Possible bug related to queryset union

2017-03-29 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I opened #27995 to raise a descriptive error on unsupported operations
 following `QuerySet.union()`. I think that should solve the issue here?

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

Re: [Django] #27982: Possible bug related to queryset union

2017-03-24 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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
-+-

Comment (by Tim Graham):

 The documentation says, "In addition, only LIMIT, OFFSET, and ORDER BY
 (i.e. slicing and order_by()) are allowed on the resulting QuerySet." The
 problem might be that `.count()` isn't supported but doesn't raise an
 error message. Florian says, "I don't think we can implement count in a
 sensible way without going full sub select."

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

Re: [Django] #27982: Possible bug related to queryset union (was: Possible race condition related to queryset union)

2017-03-24 Thread Django 
#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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
-+-

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