Ecto upsert_all partial index returning behavior gap

Ecto.Repo.upsert_all with :on_conflict on partial unique index and :returning – undefined behavior for generated columns

Sky Byte

0 reputation · 29 Oct 2021, 09:04 UTC

24K views0

When using Ecto.Repo.upsert_all/3 with :on_conflict set to a partial unique index and :returning true, it is unclear whether the returned structs contain post‑computation values for generated columns and columns altered by AFTER INSERT/UPDATE triggers.

PostgreSQL may reflect the trigger‑modified state, but MySQL and SQLite ignore :returning entirely, returning [] or a count, and Ecto’s documentation does not specify how generated column values are handled when :replace_all_except excludes them.

Does :returning include generated column values after computation? Do other adapters return empty or count only? Is conflict detection limited to rows satisfying the partial index predicate?

4,860 following

Keep exploring this topic

Preserving Original Local Time vs UTC-Normalized Storage in Ecto Schemas

Trade-off between PostgreSQL timestamptz (UTC-normalized) and naive datetime with a separate zone column for preserving original local time in Ecto schemas.

Ecto Migration Zero-Downtime Deployment Across Phoenix Application Boundaries

Migrate a small Phoenix application's database schema without service interruption. Ecto's default transaction behavior conflicts with zero-downtime requirements for large datasets.

Can a partial index on a jsonb column use ->> without casting in PostgreSQL 12?

Determine if PostgreSQL 12 permits a partial index on a jsonb column using ->> without casting and whether the planner will use that index for ->> predicates.

DataGrip retry strategies: ON CONFLICT upsert vs transaction rollback for idempotent writes

Determine the most reliable approach in DataGrip to retry failed write operations without creating duplicate records when the initial attempt partially succeeded or raised a constraint violation.

Ecto.Repo.upsert_all with :on_conflict on partial unique index and :returning – undefined behavior for generated columns

0 answers

Your perspective belongs here.

0 question comments