#16559: Switch to entity-manager type system.
---------------------------+-------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Milestone: 2.0 | Component: Uncategorized
Version: 1.3-rc1 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------+-------------------------------
I realize that I am submitting this ticket as anonymous, which will give
it reduced credibility, but at least consider the logic posted here, and
before you close this ticket, state your reason and give me time to reply.
All I am trying to do here is implement a change, that in my opinion, will
make django closer to your design philosophies.
This suggestion is mostly based on the "SQL efficiency" philosophy.
Instead of using Model.save(), you should change the framework to
implement a entity-manager approach, [http://www.doctrine-
project.org/docs/orm/2.0/en/reference/introduction.html#mini-tutorial like
doctrine does]. This would allow a one-time SQL calculation, providing
maximum efficiency. Instead of running an SQL query for each changed
model, only one query would be needed for all of them.
I realize this would be a BIG change to implement; I would recommend it
for a major release version. However, this would make django more perfect
in regard to the design philosophies, also writing less Model.save() calls
and only one em.flush() call. I hope you seriously consider this change
instead of just blowing it off; I think it would be very beneficial to
django.
--
Ticket URL: <https://code.djangoproject.com/ticket/16559>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
