Re: No support for UNION (OUTER JOIN instead)

2017-03-24 Thread guettli
Just for the records. If you think further, then deprecating is_superuser, is_staff and is_active could be a solution. See: https://groups.google.com/forum/#!topic/django-developers/J9yttc7WmJU Am Mittwoch, 15. März 2017 10:44:22 UTC+1 schrieb guettli: > > > Just for the records, I added your wo

Re: No support for UNION (OUTER JOIN instead)

2017-03-15 Thread guettli
Just for the records, I added your work-around (until Django 1.11) to as comment on the issue tracker. Am Dienstag, 14. März 2017 10:37:07 UTC+1 schrieb guettli: > > Great, you and the django dev team are fast than light. Every time I spot > a basic missing part, you have already solved it in t

Re: No support for UNION (OUTER JOIN instead)

2017-03-14 Thread guettli
Great, you and the django dev team are fast than light. Every time I spot a basic missing part, you have already solved it in the next release. Am Montag, 13. März 2017 17:00:17 UTC+1 schrieb Tim Graham: > > Support for QuerySet.union(), intersection(), and difference() is added in > Django 1.11

Re: No support for UNION (OUTER JOIN instead)

2017-03-13 Thread Tim Graham
Support for QuerySet.union(), intersection(), and difference() is added in Django 1.11. https://github.com/django/django/commit/84c1826ded17b2d74f66717fb745fc36e37949fd On Monday, March 13, 2017 at 11:54:15 AM UTC-4, guettli wrote: > > We have performance issues on postgres because some SQL stat

No support for UNION (OUTER JOIN instead)

2017-03-13 Thread guettli
We have performance issues on postgres because some SQL statements have up to six LEFT OUTER joins. Union and intersection would be easier to read for me (human being) and maybe better to optimize for the postgres query planer. It seems that other people have this issue, too: https://code.d