mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2706
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/315
Author: @aksdb
Created: 12/28/2018
Status: ✅ Merged
Merged: 12/28/2018
Merged by: @dani-garcia
Base:
master← Head:master📝 Commits (1)
e7ea509Restrict join on users_collections to current user (fixes #313)📊 Changes
1 file changed (+7 additions, -3 deletions)
View changed files
📝
src/db/models/cipher.rs(+7 -3)📄 Description
It fixes #313 at least partially ... the other part being fixed by @mprasil's PR #314.
The problem was, that when multiple users in the same collection are Admin or Owner, the previous JOIN would include multiple rows for the same cipher. The PR fixes this by restricting the joined users_collections in the first place.
(It also makes another JOIN a little more explicit.)
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.