Filipe Pina

Not sure I understand the issue. If the model does not have a "pk" field, it's expected that match_field should fail if you use the default. Just specify the one...

I was under the impression it would be otherwise actually. The default primary key is usually “id” but “pk” would always translate to the actual one (even if primary key...

Not really if you're using only `id` as match_field but also have a unique constraint on another field

Where does `currency` come from? Have you renamed to "MyModel" for posting purposes? Makes it harder to understand/help Anyway, are you sure there's not multiple objs with id 1 in...

If you're reading from a source where id is a string (instead of an int), cast it to int when assigning to the objs id/pk field. I thought that had...

bulk_create and bulk_update do not use save (nor send the signal), bulk_update_or_create doesn’t either. I’ll leave this open to remember to update the docs to highlight this, thanks

Yes the comment explains why that happens: # .create on the remaining (bulk_create won't work on multi-table inheritance models...) bulk_create doesn’t work with multi-table models (but bulk_update does and it’s...

No, not sure I understood though. Chinese use American spelling?:)

Hi @rtubio you're right (if I understood you well), `select_for_update` should be used here, to avoid concurrency issues and dataloss. Added to the ToDo

It's funny that this "fix" is delayed to v3 because it's considered "breaking change", yet a huge number of people keep burning hours pinning down this behavior. I'd say that...