3 ms·
I find Django to be very inefficient in how it handles INSERT vs. UPDATE; you're better off specifing force_insert or force_update in the call to save() to avoi
by cfinke 17y ago
I find Django to be very inefficient in how it handles INSERT vs. UPDATE; you're better off specifing force_insert or force_update in the call to save() to avoid the extra SELECT it runs, since you almost always know whether the object you're saving is new or should be updated.
- almost 17y agoBut only in the cases where it actually matters which given normal DB usage patterns for most sites is often nowhere. No point in making things more complicated when it's not needed!