Opened 5 years ago

Closed 3 years ago

#21252 closed Bug (fixed)

Positional column numbers is not always correct for ORDER BY and GROUP BY

Reported by: Michael Manfre Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


"SELECT ... GROUP BY 1 ORDER BY 1" is very fragile and may not associate with the intended column if any columns are front loaded on to the select. Columns are front loaded by extra() and could be added by 3rd party database backends.

There are discussions of no longer front loading the extra() select columns. Assuming this change happens, the problem space would be reduced to just 3rd party backends, which would need some way to know that there are positional values in the query or would need an easier way of injecting columns in to the select without resorting to the simple front loading.

Change History (3)

comment:1 Changed 5 years ago by Anssi Kääriäinen

Triage Stage: UnreviewedAccepted

I agree. Seems to be issue only in DateQueries, and hopefully that area will be improved soonish.

comment:2 Changed 3 years ago by Tim Graham

It's unclear to me what needs to be done to resolve this ticket. Michael, could you say if this is still an issue and elaborate if so?

comment:3 Changed 3 years ago by Anssi Kääriäinen

Resolution: fixed
Status: newclosed

It seems Django doesn't anymore generate queries of the form ORDER BY 1. Thus, I think we can close this ticket. If there are indeed places where Django generates such queries (instead of the user explicitly asking for such queries), then please reopen.

I'll resolve as fixed due to the fact that we have removed DateQueryset.

Note: See TracTickets for help on using tickets.
Back to Top