Re: [Django] #17: Metasystem optimization: Share select_related in memory
Django
-------------------------------------+-------------------------------------
Reporter: adrian | Owner: PhiR
Type: New | Status: closed
feature | Component: Database layer
Milestone: | (models, ORM)
Version: SVN | Severity: Normal
Resolution: wontfix | Keywords: feature caching
Triage Stage: Accepted | Has patch: 1
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: assigned => closed
* ui_ux: => 0
* resolution: => wontfix
* easy: => 0
Comment:
I've spoken to Russ, and he concurs with my decision that this would
fundamentally change the ORM, and it can't be part of Django core.
However, it's been proven that this is possible (albeit tricky) in
external packages -- JohhnyCache, for example. Concrete suggestions about
how to make things like Johnny easier are super-welcome, but for clarity
those should get fresh new tickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/17#comment:60>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
| Raoult
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: feature caching | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by James Pic):
Do you remember the discussion you had with Russ about this ?
Identity Map is a common programming pattern:
https://martinfowler.com/eaaCatalog/identityMap.html
Is this good for re-opening ?
- The ORM is much cleaner now than 7 years ago,
- Many great ORMs have a builtin Identity Map, why can't Django's ?
--
Ticket URL: <https://code.djangoproject.com/ticket/17#comment:61>
Django
-------------------------------------+-------------------------------------
Reporter: Adrian Holovaty | Owner: Philippe
| Raoult
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: feature caching | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* cc: James Pic (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/17#comment:62>
Django
-------------------------------------+-------------------------------------
Reporter: Adrian Holovaty | Owner: Philippe
| Raoult
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: feature caching | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
See TicketClosingReasons/DontReopenTickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/17#comment:63>
Django
-------------------------------------+-------------------------------------
Reporter: Adrian Holovaty | Owner: Philippe
| Raoult
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: feature caching | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by James Pic):
Thanks for the heads up Tim, will mandate a hacker to give it a try.
--
Ticket URL: <https://code.djangoproject.com/ticket/17#comment:64>