···164164165165 This is because the above functions depend on the Ecto Adapter returning the name of the violated constraint,
166166 which you annotate in your changeset so that Ecto can convert the constraint violation into the correct
167167- updated changeset when the constraint is hit during a `Ecto.Repo.update/2` or `Ecto.Repo.insert/2` operation.
167167+ updated changeset when the constraint is hit during a `m:Ecto.Repo.update/2` or `m:Ecto.Repo.insert/2` operation.
168168 Since we cannot get the name of the violated constraint back from SQLite3 at `INSERT` or `UPDATE` time,
169169 there is no way to effectively use these changeset functions. This is a SQLite3 limitation.
170170