Opened 19 years ago
Closed 19 years ago
#524 closed defect (wontfix)
Numerous excessive selects in the manipulator
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Core (Other) | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The default ChangeManipulator does a number of selects on the database which I don't want. This enlarges the DB load significantly. How to get rid of that?
The selects I mean are:
- first it gets the original object that it is supposed to work on (even though the generic view it is invoked from does that anyway)
- then it gets a list of objects that this one refers to, for each ForeignKey field (and I don't want that)
Change History (1)
comment:1 by , 19 years ago
Resolution: | → wontfix |
---|---|
Severity: | major → normal |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The solution to your problem is: Don't use the generic ChangeManipulators. Feel free to write your own manipulators and views that are trimmed down.