Paranoia to work with Uniqueness and Elastic Search

[ayza-hamid]

I used Paranoia gem for Rails 6. And it isn't working as expected. It passes the model level validations for unique columns.

PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_email" DETAIL: Key (email)=(selo@mailinator.com) already exists.

Is this gem compatible with Rails 6. Also I am facing issues while indexing. In before action call for soft delete method the indexing doesn't work and shows all the records including the deleted ones.

[rodenmonte]

This isn't a problem with Rails 6. The deleted record with email "selo@mailinator.com" is still in your users table, with its paranoia column (probably deleted_at) set. It looks like you're using postgres, so you can solve this with a partial index, instead of create unique index index_users_on_email on users (email), try create unique index index_users_on_email_paranoid on users (email) where deleted_at is null or similar.

The readme explains better: https://github.com/rubysherpas/paranoia/blob/core/README.md#unique-indexes