Release v3.13.0

Author: josevalim

CHANGELOG.md

@@ -16,13 +16,19 @@ Requires Elixir v1.14+.
   * [Ecto.Query] Allow source fields in `json_extract_path`
   * [Ecto.Repo] Add `Ecto.Repo.prepare_transaction/2` user callback
   * [Ecto.Repo] Add `Ecto.Repo.all_by/3`
+  * [Ecto.Repo] Add `Ecto.Repo.transact/2`
+  * [Ecto.Repo] Allow HOT updates on upsert queries in Postgres by removing duplicate fields during `replace` and `replace_all_except`
   * [Ecto.Schema] Support `@schema_redact: :all_except_primary_keys` module attribute
 
 ### Bug fixes
 
   * [Ecto.Query] Allow select merging maps with all nil values
   * [Ecto.Schema] Fix an issue where Ecto could warn an association did not exist, when it did
 
+### Deprecations
+
+  * [Ecto.Repo] `Ecto.Repo.transaction/2` is soft-deprecated in favor of `Ecto.Repo.transaction/1`
+
 ## v3.12.6 (2025-06-11)
 
 Fix deprecations on Elixir v1.19.
@@ -85,7 +91,7 @@ Fix deprecations on Elixir v1.19.
   * [Ecto.Query] Allow map updates with dynamic values in `select`
   * [Ecto.Query] Allow any data structure that implements the Enumerable protocol on the right side of `in`
   * [Ecto.Repo] Support 2-arity preload functions that receive ids and the association metadata
-  * [Ecto.Repo] Allow Hot Updates on upsert queries in Postgres by removing duplicate fields during replace_all
+  * [Ecto.Repo] Allow HOT updates on upsert queries in Postgres by removing duplicate fields during `replace_all`
   * [Ecto.Repo] `insert_all` supports queries with only source
   * [Ecto.Repo] `insert_all` supports queries with the update syntax
   * [Ecto.Repo] Support `:allow_stale` on Repo struct/changeset operations

lib/ecto/repo.ex

@@ -2180,6 +2180,8 @@ defmodule Ecto.Repo do
   @doc """
   Runs the given function or `Ecto.Multi` inside a transaction.
 
+  Deprecated in favor of `c:transact/2`.
+
   ## Use with function
 
   `c:transaction/2` can be called with both a function of arity
@@ -2209,42 +2211,7 @@ defmodule Ecto.Repo do
   A successful transaction returns the value returned by the function
   wrapped in a tuple as `{:ok, value}`.
 
-  ### Nested transactions
-
-  If `c:transaction/2` is called inside another transaction, the function
-  is simply executed, without wrapping the new transaction call in any
-  way. If there is an error in the inner transaction and the error is
-  rescued, or the inner transaction is rolled back, the whole outer
-  transaction is aborted, guaranteeing nothing will be committed.
-
-  Below is an example of how rollbacks work with nested transactions:
-
-      {:error, :rollback} =
-        MyRepo.transaction(fn ->
-          {:error, :posting_not_allowed} =
-            MyRepo.transaction(fn ->
-              # This function call causes the following to happen:
-              #
-              #   * the transaction is rolled back in the database,
-              #   * code execution is stopped within the current function,
-              #   * and the value, passed to `rollback/1` is returned from
-              #     `MyRepo.transaction/1` as the second element in the error
-              #     tuple.
-              #
-              MyRepo.rollback(:posting_not_allowed)
-
-              # `rollback/1` stops execution, so code here won't be run
-            end)
-
-          # The transaction here is now aborted and any further
-          # operation will raise an exception.
-        end)
-
-  See the ["Aborted transactions"](`c:transaction/2#aborted-transactions`) section for more examples of aborted
-  transactions and how to handle them.
-
-  In practice, managing nested transactions can become complex quickly.
-  For this reason, Ecto provides `Ecto.Multi` for composing transactions.
+  See `c:transact/2` for further considerations.
 
   ## Use with Ecto.Multi
 
@@ -2265,63 +2232,6 @@ defmodule Ecto.Repo do
 
   Explore the `Ecto.Multi` documentation to learn more and find detailed examples.
 
-  ## Aborted transactions
-
-  When an operation inside a transaction fails, the transaction is aborted in the database.
-  For instance, if you attempt an insert that violates a unique constraint, the insert fails
-  and the transaction is aborted. In such cases, any further operation inside the transaction
-  will raise exceptions.
-
-  Take the following transaction as an example:
-
-      Repo.transaction(fn repo ->
-        case repo.insert(changeset) do
-          {:ok, post} ->
-            repo.insert(%Status{value: "success"})
-
-          {:error, changeset} ->
-            repo.insert(%Status{value: "failure"})
-        end
-      end)
-
-  If the changeset is valid, but the insert operation fails due to a database constraint,
-  the subsequent `repo.insert(%Status{value: "failure"})` operation will raise an exception
-  because the database has already aborted the transaction and thus making the operation invalid.
-  In Postgres, the exception would look like this:
-
-      ** (Postgrex.Error) ERROR 25P02 (in_failed_sql_transaction) current transaction is aborted, commands ignored until end of transaction block
-
-  If the changeset is invalid before it reaches the database due to a validation error,
-  no statement is sent to the database, an `:error` tuple is returned, and `repo.insert(%Status{value: "failure"})`
-  operation will execute as usual.
-
-  We have two options to deal with such scenarios:
-
-  If you don't want to change the semantics of your code,  you can also use the savepoints
-  feature by passing the `:mode` option like this: `repo.insert(changeset, mode: :savepoint)`.
-  In case of an exception, the transaction will rollback to the savepoint and prevent
-  the transaction from failing.
-
-  Another alternative is to handle this operation outside of the transaction.
-  For example, you can choose to perform an explicit `repo.rollback` call in the
-  `{:error, changeset}` clause and then perform the `repo.insert(%Status{value: "failure"})` outside
-  of the transaction. You might also consider using `Ecto.Multi`, as they automatically
-  rollback whenever an operation fails.
-
-  ## Working with processes
-
-  The transaction is per process. A separate process started inside a
-  transaction won't be part of the same transaction and will use a separate
-  connection altogether.
-
-  When using the `Ecto.Adapters.SQL.Sandbox` in tests, while it may be
-  possible to share the connection between processes, the parent process
-  will typically hold the connection until the transaction completes. This
-  may lead to a deadlock if the child process attempts to use the same connection.
-  See the docs for
-  [`Ecto.Adapters.SQL.Sandbox`](https://hexdocs.pm/ecto_sql/Ecto.Adapters.SQL.Sandbox.html)
-  for more information.
-
   ## Options
 
   See the ["Shared options"](#module-shared-options) section at the module

mix.exs

@@ -2,7 +2,7 @@ defmodule Ecto.MixProject do
   use Mix.Project
 
   @source_url "https://github.com/elixir-ecto/ecto"
-  @version "3.13.0-dev"
+  @version "3.13.0"
 
   def project do
     [

mix.lock

@@ -1,7 +1,7 @@
 %{
   "decimal": {:hex, :decimal, "2.3.0", "3ad6255aa77b4a3c4f818171b12d237500e63525c2fd056699967a3e7ea20f62", [:mix], [], "hexpm", "a4d66355cb29cb47c3cf30e71329e58361cfcb37c34235ef3bf1d7bf3773aeac"},
-  "earmark_parser": {:hex, :earmark_parser, "1.4.43", "34b2f401fe473080e39ff2b90feb8ddfeef7639f8ee0bbf71bb41911831d77c5", [:mix], [], "hexpm", "970a3cd19503f5e8e527a190662be2cee5d98eed1ff72ed9b3d1a3d466692de8"},
-  "ex_doc": {:hex, :ex_doc, "0.37.2", "2a3aa7014094f0e4e286a82aa5194a34dd17057160988b8509b15aa6c292720c", [:mix], [{:earmark_parser, "~> 1.4.42", [hex: :earmark_parser, repo: "hexpm", optional: false]}, {:makeup_c, ">= 0.1.0", [hex: :makeup_c, repo: "hexpm", optional: true]}, {:makeup_elixir, "~> 0.14 or ~> 1.0", [hex: :makeup_elixir, repo: "hexpm", optional: false]}, {:makeup_erlang, "~> 0.1 or ~> 1.0", [hex: :makeup_erlang, repo: "hexpm", optional: false]}, {:makeup_html, ">= 0.1.0", [hex: :makeup_html, repo: "hexpm", optional: true]}], "hexpm", "4dfa56075ce4887e4e8b1dcc121cd5fcb0f02b00391fd367ff5336d98fa49049"},
+  "earmark_parser": {:hex, :earmark_parser, "1.4.44", "f20830dd6b5c77afe2b063777ddbbff09f9759396500cdbe7523efd58d7a339c", [:mix], [], "hexpm", "4778ac752b4701a5599215f7030989c989ffdc4f6df457c5f36938cc2d2a2750"},
+  "ex_doc": {:hex, :ex_doc, "0.38.2", "504d25eef296b4dec3b8e33e810bc8b5344d565998cd83914ffe1b8503737c02", [:mix], [{:earmark_parser, "~> 1.4.44", [hex: :earmark_parser, repo: "hexpm", optional: false]}, {:makeup_c, ">= 0.1.0", [hex: :makeup_c, repo: "hexpm", optional: true]}, {:makeup_elixir, "~> 0.14 or ~> 1.0", [hex: :makeup_elixir, repo: "hexpm", optional: false]}, {:makeup_erlang, "~> 0.1 or ~> 1.0", [hex: :makeup_erlang, repo: "hexpm", optional: false]}, {:makeup_html, ">= 0.1.0", [hex: :makeup_html, repo: "hexpm", optional: true]}], "hexpm", "732f2d972e42c116a70802f9898c51b54916e542cc50968ac6980512ec90f42b"},
   "jason": {:hex, :jason, "1.4.1", "af1504e35f629ddcdd6addb3513c3853991f694921b1b9368b0bd32beb9f1b63", [:mix], [{:decimal, "~> 1.0 or ~> 2.0", [hex: :decimal, repo: "hexpm", optional: true]}], "hexpm", "fbb01ecdfd565b56261302f7e1fcc27c4fb8f32d56eab74db621fc154604a7a1"},
   "makeup": {:hex, :makeup, "1.2.1", "e90ac1c65589ef354378def3ba19d401e739ee7ee06fb47f94c687016e3713d1", [:mix], [{:nimble_parsec, "~> 1.4", [hex: :nimble_parsec, repo: "hexpm", optional: false]}], "hexpm", "d36484867b0bae0fea568d10131197a4c2e47056a6fbe84922bf6ba71c8d17ce"},
   "makeup_elixir": {:hex, :makeup_elixir, "1.0.1", "e928a4f984e795e41e3abd27bfc09f51db16ab8ba1aebdba2b3a575437efafc2", [:mix], [{:makeup, "~> 1.0", [hex: :makeup, repo: "hexpm", optional: false]}, {:nimble_parsec, "~> 1.2.3 or ~> 1.3", [hex: :nimble_parsec, repo: "hexpm", optional: false]}], "hexpm", "7284900d412a3e5cfd97fdaed4f5ed389b8f2b4cb49efc0eb3bd10e2febf9507"},