-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validates value uniqueness issue #553
Comments
Also, I saw that there was #500, which looks like a similar thing but I didn't want to hijack that for my own purposes. |
kind of a boring workaround, but you could add |
If you're using PostgreSQL you should use partial indexes (see docs). Try replacing: t.index "lower((email)::text)", name: "index_clients_on_lower_email", unique: true with t.index "lower((email)::text)", name: "index_clients_on_lower_email", unique: true, where: 'deleted_at IS NOT NULL' |
I face the same issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given the following:
If I try and create a new client with the same email as a "deleted" client I get the following error:
What I was expecting to happen was that it would trigger an "email is already taken" validation error because I have
without_default_scope: true
, so it should check against all clients, not just the non-deleted ones.Is this what should be happening and something is wrong, or am I incorrect and need to do something else to validate against all clients.
I'm using:
Ruby 3.3.0
Rails 7.1.3.2
Paranoia 2.6.3
The text was updated successfully, but these errors were encountered: