Skip to content
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

[PM-1191] collections cannot be managed in family organization #2765

Conversation

coroiu
Copy link
Contributor

@coroiu coroiu commented Mar 3, 2023

Type of change

- [x] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Fix issue reported by users that org vault is broken after OAVR v2 when using EF.

Fixes #2750

Code changes

EF6 is currently not able to translate LINQ that include selects after group statements (see github issue). Using join let's us bypass this issue.

This new solution is probably a bit faster too so win-win :)

Before you submit

  • Please check for formatting errors (dotnet format --verify-no-changes) (required)
  • If making database changes - make sure you also update Entity Framework queries and/or migrations
  • Please add unit tests where it makes sense to do so (encouraged but not required)
  • If this change requires a documentation update - notify the documentation team
  • If this change has particular deployment requirements - notify the DevOps team

EF6 is currently not able to translate LINQ that include selects after groupby statements. Using join let's us bypass this issue.
@coroiu coroiu changed the title Pm 1191 collections cannot be managed in family organization [PM-1191] collections cannot be managed in family organization Mar 3, 2023
jlf0dev
jlf0dev previously approved these changes Mar 3, 2023
@coroiu coroiu added the needs-qa label Mar 3, 2023
@justindbaur
Copy link
Member

justindbaur commented Mar 3, 2023

@coroiu Maybe I am missing something but isn't this now saying every collection has access groups and users associated to it if ANY do?

I have a group that only has the Default Collection:
image

But two collection show that they have that group assigned.

image

Copy link
Member

@justindbaur justindbaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above concern

@coroiu
Copy link
Contributor Author

coroiu commented Mar 3, 2023

Nice catch, should be fixed now! Guess I “simplified queries” a bit too much 😅

Copy link
Member

@justindbaur justindbaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks.

@cvondra
Copy link

cvondra commented Mar 6, 2023

If these changes were approved why are they not being pulled into the dev build?

@coroiu
Copy link
Contributor Author

coroiu commented Mar 7, 2023

@cvondra waiting for QA, if vault team has different processes then feel free to merge :)

@cvondra
Copy link

cvondra commented Mar 7, 2023

@justindbaur any idea on the QA status of this?

@justindbaur
Copy link
Member

@coroiu Part of the reason that unified is in beta is because QA doesn't have infrastructure or capacity to test each feature branch right now for EF databases. Since this is an EF change only and I ran it locally we can just merge this.

@cvondra I'm going to merge this now and it will be in the dev tag shortly.

@justindbaur justindbaur merged commit 2c9df6d into master Mar 7, 2023
@justindbaur justindbaur deleted the PM-1191-collections-cannot-be-managed-in-family-organization branch March 7, 2023 13:35
@cvondra
Copy link

cvondra commented Mar 7, 2023

Latest push to /dev works perfectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Collections cannot be managed in family organization
4 participants