Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Can We Integrate Save The Change into Django's Core? #1
Djagno ticket #4102 discusses adding a feature like this, but was changed into adding the
I think there are a number of reasons perhaps not to add this to Django proper. They're not necessarily all valid, but here's how I see it:
The counterargument here is that there'd be a group who prefer this more granular update by default. If, for example, two users update the same news article at the same time, one adjusting the slug, and the other changing some of the body text, this granular save would have a preferable effect: both improvements to the article would be made; one wouldn't block out the other.
Of course, I've done everything possible to minimize memory usage:
And honestly, this might make the overall operation slower. It certainly makes the actual database write faster, and that's awesome if you're me, but it's not necessarily what everyone else wants (a slower overall save for a faster db write).
Then again, I didn't spend much time trying to get it to work, I just assumed that it wasn't possible as I was told as much. Perhaps it's completely doable with a little bit (but not a ton) of work.