Opened 16 years ago
Closed 13 years ago
#10499 closed New feature (wontfix)
Maybe make _default_manager part of the public API
Reported by: | Malcolm Tredinnick | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Moving the "design-decision-needed" portion of #9676 over here. The contention is that some applications might need access to _default_manager
and so it should be part of the public API.
Needs more thinking about the problem space before a decision can be reached here. Certainly post-1.1.
Change History (3)
comment:1 by , 16 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:3 by , 13 years ago
Easy pickings: | unset |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
UI/UX: | unset |
Note:
See TracTickets
for help on using tickets.
Given that nothing happened here for three years, I assume that there isn't much demand for making _default_manager a public API.