I'm attempting to implement narrow writes (that is, writing only fields which have changed).
I would be able to do this as a 3rd-party Mixin library if some changes were made to Model.save_base. 1) returned whether the row was created or updated, e.g. if .save_base returned the `updated` value which it uses to send the .post_save signal. 2) raise something finer-grained than DatabaseError when force_update is used (so that I could then try a (wide) insert-or-update. The new exception could inherit from DatabaseError for backwards-compat. Any objections to me making these changes? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAM0i3f5tnHVeHeNA5cqXOzTyN-S6YbjBRtOZm7o0-noLSHiQdQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
