Changes between Version 1 and Version 2 of Ticket #34262, comment 17


Ignore:
Timestamp:
Feb 19, 2025, 2:12:40 PM (3 days ago)
Author:
ontowhee

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34262, comment 17

    v1 v2  
    1818- The filter clause is leveraging the existing filter implementation for expressions. For MySQL, this means it creates CASE() instead of FILTER(). MySQL does not support [https://modern-sql.com/feature/filter filter clause].
    1919- The chart in the article shows a lightning bolt MySQL. I may be misunderstanding what that means, but I have not been able to directly run a “ANY_VALUE() FILTER() OVER()” expression. I tried to keep the scope of this ticket simple by not addressing this one for now.
    20 - For the specific case described in this ticket, instead of creating the django expression `AnyValue(Least("min_pages", "greatest_page"))` , the tests are creating `Least("min_pages", AnyValue("greatest_page"))`. It wraps AnyValue() on "greatest_page" instead of the entire expression. This avoids the error that is raised `Cannot compute ... is an aggregate` error in `resolve_expression`.
     20- For the specific case described in this ticket, instead of creating the django expression `AnyValue(Least("min_pages", "greatest_page"))` , the tests are creating `Least("min_pages", AnyValue("greatest_page"))`. It wraps AnyValue() on "greatest_page" instead of the entire expression. This avoids the error that is raised `Cannot compute ... is an aggregate` error in `resolve_expression`, and it seems to make sense now that all the columns have an "aggregate" function operating on them.
Back to Top