Opened 14 years ago
Last modified 12 months ago
#16429 new New feature
Add configurable caching to FilePathField — at Initial Version
| Reported by: | Daniel Swarbrick | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Carlton Gibson, David Smith | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | |||
Description ¶
As noted by a couple of people on django-users, FilePathField does not automatically refresh choices if files are add to or removed from the path being pointed to (http://groups.google.com/group/django-users/browse_thread/thread/6778fa138b848996 and http://groups.google.com/group/django-users/browse_thread/thread/403d872cf9433905).
A nice addition to FilePathField would be the ability to control how long the choices are cached for, ranging from "never cached" to "cached forever" (or at least for the lifetime of the webserver process).
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR].
Note:
See TracTickets
for help on using tickets.