WIP MDEV-35168: Potential Bug in Database Handling of NULL Values in EXIS… #4327
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…TS Clause
Queries of the form
must force derived table
dtto be materialized, or theWHERE EXISTSwill not filter rows correctly. If we allow derived tabledtto be merged, then references todt.alias_Nare replaced with their constant values directly, so aWHERE EXISTSsubquery will attempt to filter rows from the outer query based on those constant values rather than the columns' values computed during outer query evaluation.Note that this is a WIP