Fixed #32546 -- Avoided Meta.ordering columns in GROUP BY clauses.
PR #14122 ↗ · django/django · · merged Mar 16, 2021 · +16−6 · base bc04941bf811
Agent prompt
what a new run launched now would send
Meta.ordering fields must not be included in GROUP BY clause
Description
This continues (closed) [1] ticket.
I beleave it was not properly fixed in commit [0ddb4ebf].
While commit [0ddb4ebf] removes ORDER BY when Meta.ordering is used it still does populates GROUP BY with Meta.ordering fields thus leads to wrong aggregation.
PR with test case was added at [2].
[1] https://code.djangoproject.com/ticket/14357
[2] https://github.com/django/django/pull/14122
Work only inside this repository checkout. Make the code change the task
describes, keeping the diff focused — no drive-by refactors.
When you are done, leave your changes committed or in the working tree;
they are collected automatically.
Stay on this snapshot checkout (`task/ycb_django_pr14122`). Never checkout, pull, or rebase onto `main`. That branch is a README-only orphan.
Stay on this HEAD. Do not fetch another default branch. Push only on the Cursor-created `crazy-cursor/…` side branch from this HEAD.
Some past runs of this task were launched with a different prompt (the prompt template changed since, or those runs predate this benchmark's stored prompt). Each run persists the exact prompt it sent at launch — that per-launch record is the audit trail; this page shows only the current one.
Reference diff
The task PR's merged diff — the judge's comparison target.