You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently with on_conflict(...).insert(...) (as well as insert_and_get and bulk_insert) there is no way to know which rows were inserted and which have been updated in-place (unlike Django's update_or_create which returns a tuple of obj, created).
Currently with
on_conflict(...).insert(...)
(as well asinsert_and_get
andbulk_insert
) there is no way to know which rows were inserted and which have been updated in-place (unlike Django'supdate_or_create
which returns a tuple ofobj, created
).However, Postgres provides such trick with
RETURNING *, (xmax = 0)
(see https://stackoverflow.com/a/47001830/189806).It would be great if that was supported natively by the library.
The text was updated successfully, but these errors were encountered: