#30207: Optimise paginator for tables with massive records
-------------------------------------+-------------------------------------
Reporter: M. Javidan Darugar | Owner: M.
Type: | Javidan Darugar
Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by M. Javidan Darugar):
* status: closed => new
* resolution: needsinfo =>
Comment:
I reopen this ticket because it is not solved yet, if I am replying to
messages by delay it is because I have a full time job and rarely have
time to work on a side project but still love to contribute to the django
community.
Some of the comments in the github branch was about naming for variable or
function arguments which means there is no standards for naming for
variables because everyone can suggest something new.
Another comment was too irrelevant about what I proposed. If postgres has
a new feature it does not mean that it is good for django because django
has an ORM which should work with other databases as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/30207#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.518da6025b8db042b20290628a3727ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
