django.git/django/db/models/sql/query.py, branch 3.2.2 django http://cgit.adnoto.dev/django.git/atom?h=3.2.2 2021-04-28T18:27:42Z [3.2.x] Fixed #32632, Fixed #32657 -- Removed flawed support for Subquery deconstruction. 2021-04-28T18:27:42Z Simon Charette charette.s@gmail.com 2021-04-24T05:07:18Z urn:sha1:d5add5d3a26f98e961dfbcad67bb04d936f2f332 Subquery deconstruction support required implementing complex and expensive equality rules for sql.Query objects for little benefit as the latter cannot themselves be made deconstructible to their reference to model classes. Making Expression @deconstructible and not BaseExpression allows interested parties to conform to the "expression" API even if they are not deconstructible as it's only a requirement for expressions allowed in Model fields and meta options (e.g. constraints, indexes). Thanks Phillip Cutter for the report. This also fixes a performance regression in bbf141bcdc31f1324048af9233583a523ac54c94. Backport of c8b659430556dca0b2fe27cf2ea0f8290dbafecd from main [3.2.x] Fixed #32650 -- Fixed handling subquery aliasing on queryset combination. 2021-04-21T08:32:39Z Simon Charette charette.s@gmail.com 2021-04-21T02:25:52Z urn:sha1:48e19bae49f271cccbb8a8f4549c9366b7cecac6 This issue started manifesting itself when nesting a combined subquery relying on exclude() since 8593e162c9cb63a6c0b06daf045bc1c21eb4d7c1 but sql.Query.combine never properly handled subqueries outer refs in the first place, see QuerySetBitwiseOperationTests.test_subquery_aliases() (refs #27149). Thanks Raffaele Salmaso for the report. Backport of 6d0cbe42c3d382e5393d4af48185c546bb0ada1f from main [3.2.x] Fixed #32478 -- Included nested columns referenced by subqueries in GROUP BY on aggregations. 2021-02-24T09:11:37Z Simon Charette charette.s@gmail.com 2021-02-24T01:56:29Z urn:sha1:7a6ca01f4eb990772080e2978f19d83484184b04 Regression in fb3f034f1c63160c0ff13c609acd01c18be12f80. Refs #31094, #31150. Thanks Igor Pejic for the report. Backport of 277eea8fcced7f04f3800617f189beb349a3212e from master Fixed #32231 -- Allowed passing None params to QuerySet.raw(). 2021-01-05T09:37:11Z Alexander Lyabah a.lyabah@checkio.org 2020-11-28T16:08:27Z urn:sha1:415f50298f97fb17f841a9df38d995ccf347dfcc Fixed #25534, Fixed #31639 -- Added support for transform references in expressions. 2020-11-27T19:42:04Z Ian Foote python@ian.feete.org 2020-11-15T22:43:47Z urn:sha1:8b040e3cbbb2e81420e777afc3ca48a1c8f4dd5a Thanks Mariusz Felisiak and Simon Charette for reviews. Fixed #31507 -- Added QuerySet.exists() optimizations to compound queries. 2020-11-16T19:29:13Z David-Wobrock david.wobrock@gmail.com 2020-11-11T22:16:32Z urn:sha1:ba42569d5c01b58b2999e393f097b530e538ec41 Fixed #31496 -- Fixed QuerySet.values()/values_list() crash on combined querysets ordered by annotations. 2020-11-14T09:22:09Z David-Wobrock david.wobrock@gmail.com 2020-10-10T15:41:13Z urn:sha1:464a4c0c59277056b5d3c1132ac1b4c6085aee08 Fixed #31910 -- Fixed crash of GIS aggregations over subqueries. 2020-11-04T08:54:58Z Simon Charette charette.s@gmail.com 2020-11-03T21:50:10Z urn:sha1:c2d4926702045e342a668057f0a758eec9db9436 Regression was introduced by fff5186 but was due a long standing issue. AggregateQuery was abusing Query.subquery: bool by stashing its compiled inner query's SQL for later use in its compiler which made select_format checks for Query.subquery wrongly assume the provide query was a subquery. This patch prevents that from happening by using a dedicated inner_query attribute which is compiled at a later time by SQLAggregateCompiler. Moving the inner query's compilation to SQLAggregateCompiler.compile had the side effect of addressing a long standing issue with aggregation subquery pushdown which prevented converters from being run. This is now fixed as the aggregation_regress adjustments demonstrate. Refs #25367. Thanks Eran Keydar for the report. Fixed #32152 -- Fixed grouping by subquery aliases. 2020-10-29T08:56:09Z Christian Klus christianklus@gmail.com 2020-10-27T18:13:10Z urn:sha1:4ac2d4fa42e1659f328c35b6b8d4761b3419c11a Regression in 42c08ee46539ef44f8658ebb1cbefb408e0d03fe. Thanks Simon Charette for the review. Fixed #32143 -- Used EXISTS to exclude multi-valued relationships. 2020-10-28T06:22:00Z Simon Charette charette.s@gmail.com 2020-10-25T20:04:21Z urn:sha1:8593e162c9cb63a6c0b06daf045bc1c21eb4d7c1 As mentioned in the pre-existing split_exclude() docstring EXISTS is easier to optimize for query planers and circumvents the IN (NULL) handling issue.