We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 3db4da0 commit 3cbc1ccCopy full SHA for 3cbc1cc
lib/ecto/adapters/sqlite3.ex
@@ -164,7 +164,7 @@ defmodule Ecto.Adapters.SQLite3 do
164
165
This is because the above functions depend on the Ecto Adapter returning the name of the violated constraint,
166
which you annotate in your changeset so that Ecto can convert the constraint violation into the correct
167
- updated changeset when the constraint is hit during a `Ecto.Repo.update/2` or `Ecto.Repo.insert/2` operation.
+ updated changeset when the constraint is hit during a `m:Ecto.Repo.update/2` or `m:Ecto.Repo.insert/2` operation.
168
Since we cannot get the name of the violated constraint back from SQLite3 at `INSERT` or `UPDATE` time,
169
there is no way to effectively use these changeset functions. This is a SQLite3 limitation.
170
0 commit comments