#32346 closed New feature (invalid)
Expose ROW_NUMBER functionality.
| Reported by: | Stuart Axon | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.1 |
| Severity: | Normal | Keywords: | row_number, iterator |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
ROW_NUMBER opens up possibilities for users to optimise queries.
It is supported in all the major databases:
Oracle: ROW_NUMBER
Postgres: ROW_NUMBER
MYSQL: ROW_NUMBER since 8.0
Sqlite: ROW_NUMBER since 3.25.0
MSSQL: ROW_NUMBER all supported versions
Supporting it would help in use cases where the user is building records that currently use python enumerate.
I'm not sure what a django-esque name would be, there are probably better ones than row_number.
Note:
See TracTickets
for help on using tickets.
It's already supported using the
RowNumberdatabase function since Django 2.0.https://github.com/django/django/blob/4c62cdaa1041d49d0b46f6cef5f4618f020fff29/django/db/models/functions/window.py#L105-L108