-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Query: add validation to warn about required navigations pointing to entity with query filter #19801
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
Design meeting decision:
|
maumar
added a commit
that referenced
this issue
May 22, 2020
…ons pointing to entity with query filter Warning is issued for required navigations for which required side has query filter and the optional side doesn't. When both sides define query filters we assume they are correct, i.e. we don't peek inside the filters to make sure they are consistent. Fixes #19801
maumar
added a commit
that referenced
this issue
May 22, 2020
…ons pointing to entity with query filter Warning is issued for required navigations for which required side has query filter and the optional side doesn't. When both sides define query filters we assume they are correct, i.e. we don't peek inside the filters to make sure they are consistent. Fixes #19801
maumar
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
May 22, 2020
maumar
added a commit
that referenced
this issue
May 22, 2020
…ons pointing to entity with query filter Warning is issued for required navigations for which required side has query filter and the optional side doesn't. When both sides define query filters we assume they are correct, i.e. we don't peek inside the filters to make sure they are consistent. Fixes #19801
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
When model has required navigation which points to the entity, which has query filter we could run into a problematic situation. If the entity is filtered out by query filter we run into referential integrity issue (required entity is not there), so currently we remove the parent entity also. This might be unexpected - we should detect this case during model validation.
Ideally this case would be handled by having a query filter also on the other side of the navigation, effectively filtering out entities whose other side of the navigation has been pruned by it's query filter (soft cascade delete of sorts)
The text was updated successfully, but these errors were encountered: