+1
Looking at the PR it looks like a boolean is still an accepted value for
force_insert which is nice as the feature looks to be used quite a bit
(just a rough idea
https://github.com/search?type=code&auto_enroll=true&q=force_insert%3DTrue).
Might be a stupid question, reading the
docs
http
Sarah, not a stupid question at all.
While `force_update` is a somewhat opposite of `force_insert` there are
nuances in how they are handled in the face of MTI (multi-table
inheritance).
The proposed issubclass'esque additional signature (ModelBase |
tuple[ModelBase]) works in the case of `for
Also the current method initially tries to UPDATE, if not UPDATED then it
tries to INSERT. So the case of having consecutive UPDATES is already
optimized with minimum possible number of queries.
On Friday, June 9, 2023 at 12:10:18 AM UTC+5:30 charettes wrote:
> Sarah, not a stupid question at a
