mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-02-16 23:31:40 +03:00
Because of differences in how .on_conflict() works compared to .replace_into() the PostgreSQL backend wasn't correctly ensuring the unique constraint on user_uuid and atype wasn't getting violated. This change simply issues a DELETE on the unique constraint prior to the insert to ensure uniqueness. PostgreSQL does not support multiple constraints in ON CONFLICT clauses. |
||
---|---|---|
.. | ||
models | ||
schemas | ||
mod.rs |