Repository navigation
unique_constraint not working #202
Description
As pointed out on README unique_constraint doesn't work as expected (modifying changeset errors) and instead raising an exception.
There are any plans to implement or improve this or it's totally impossible to give support for this validation because SQLite special characteristics?
Activity
scouten commentedon Oct 14, 2017
SQLite does not tell you which constraint has been violated, so it's not possible to properly complete the Ecto error response. This is not a great answer, but I'm at a loss for how to improve on it. Suggestions?
jfcalvo commentedon Oct 18, 2017
I don't have the necessary knowledge about SQLite to think in a correct solution sorry.
But a possible workaround could be to use
unsafe_validate_uniquein your changesets so you have at least a previous (and sadly unsafe) validation.roylez commentedon May 10, 2018
The follow is what I get from running ecto integration. I think the error message does tell which constraint has been violated.
scouten commentedon Jun 17, 2018
As noted in the recently-updated README, I am no longer able to actively maintain this project due to some other life circumstances.
I'll review a patch if one comes or transfer ownership to a new maintainer if somebody signals an interest in taking over.
Closes elixir-sqlite#202 - Basic support for UNIQUE constraint change…