Thank you very much for the insight and thorough explanations. I’d like to be proven wrong but I don’t think Ecto actually can do things substantially differently in order to avoid side effects on PostgreSQL side.
silverdr
alexandre
Where is this documented? I can’t find anything about that in the insert options documentation.
0
LostKobrakai
This is not a behaviour ecto controls. It’s how postgres works.
The optional
RETURNINGclause causesINSERTto compute and return value(s) based on each row actually inserted (or updated, if anON CONFLICT DO UPDATEclause was used).
2
alexandre
Thank you! Also, I just found this below, posting here for future reference of others:
While the above won’t raise an error in case of conflicts, it also won’t update the struct given, so it will return a tag without ID. One solution is to force an update to happen in case of conflicts, even if the update is about setting the tag name to its current name.
0