Changes between Version 4 and Version 5 of Ticket #34978, comment 4


Ignore:
Timestamp:
Nov 20, 2023, 9:29:57 AM (12 months ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34978, comment 4

    v4 v5  
    55553. Adjust the 4.2 existing release notes about this change to better communicate that this version of Django removed support for doing `RawSQL` aggregations on MySQL and that they should use proper expressions instead going forward.
    5656
    57 Due to lack of demonstration that some aggregates or window function cannot be expressed using the advanced ORM primitives, that non-`ONLY_FULL_GROUP_BY` model is a non standard MySQL feature that is not enabled by default since 8.0, and that this change happen to standardize the usage of `RawSQL` for aggregations on all backends I'd be inclined to go with 3.
     57Due to lack of demonstration that some aggregates or window function cannot be expressed using the documented primitives offered by the ORM, that non-`ONLY_FULL_GROUP_BY` model is a non standard MySQL feature that is not enabled by default since 8.0, and that this change happens to standardize the usage of `RawSQL` for aggregations on all backends I'd be inclined to go with 3.
Back to Top