Switch to entity-manager type system.
|Reported by:||anonymous||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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, 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.