Skip to content

Fix-indirect-(2nd-level)-teile-lookup-in-solutionQuery-for-DQL-task-79#6

Open
max-schmitz wants to merge 1 commit intoEILD-nrw:mainfrom
max-schmitz:Fix-indirect-(2nd-level)-teile-lookup-in-solutionQuery-for-DQL-task-79
Open

Fix-indirect-(2nd-level)-teile-lookup-in-solutionQuery-for-DQL-task-79#6
max-schmitz wants to merge 1 commit intoEILD-nrw:mainfrom
max-schmitz:Fix-indirect-(2nd-level)-teile-lookup-in-solutionQuery-for-DQL-task-79

Conversation

@max-schmitz
Copy link
Copy Markdown

fix second-level part filtering and refactor solutionQuery to use explicit JOINs

In the old query the indirect-filtering-part contained the two conditions 'unter.uteil = ober.oteil AND unter.uteil = 3'
which effectively required 'ober.oteil = 3', so it only checks if teil 3 is child of teil 3 but not if there are teile that use teil 3 indirectly at the second level.
This change now truly returns indirectly used teile at the second level, introduces distinct aliases (s0, s1), that make the hierarchy unambiguous and uses ANSI-style explicit joins.

…licit JOINs

In the old query the indirect-filtering-part contained the two conditions 'unter.uteil = ober.oteil AND unter.uteil = 3'
which effectively required 'ober.oteil = 3', so it only checks if teil 3 is child of teil 3 but not if there are teile that use teil 3 indirectly at the second level.
This change now truly returns indirectly used teile at the second level, introduces distinct aliases (s0, s1), that make the hierarchy unambiguous and uses ANSI-style explicit joins.
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.

1 participant