Now that AshPostgres supports `MERGE`, we can finally have `Ash.update_many/4` in #AshFramework 😎. This allows you to do many row-wise updates each with their own unique input. This differs from `Ash.bulk_update/4` which updates a query or a set of records with *one* set of inputs. This might not seem that cool, but try hand-rolling this in a re-usable way with all of the various features that Ash supports (atomics, expression-based-updates, lifecycle hooks, etc.) and you'll get it 😂 This can be used for all kinds of purposes, but will soon be used to significantly optimize relationship management logic, i.e updating a to_many relationship with a set of inputs will now be three discrete queries, one to create anything new, one to update anything modified (with `update_many`) and one to remove anything left out. Take a look at the example code & representative SQL query: #ElixirLang

Small thing I'm weirdly excited about in the next release of AshPostgres: upserts can now tell you whether each record was inserted or updated. Sometimes it is fun to work on fancy new packages for #AshFramework, but being able to focus on the core stuff is often more rewarding. This might sound easy, but the standard "INSERT ... ON CONFLICT" approach cannot generalize this without resorting to hacks that don't generalize to any given use case. Now you can just read `:upsert_action` from the result metadata — works for a single record or a whole bulk upsert. It's powered by a SQL `MERGE` under the hood now (PG17+), which also quietly sets up something much bigger I'll be sharing soon 👀 Just have to update the `min_pg_version` callback on your repo to take advantage of it #ElixirLang