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

Add handling of index hints on join clauses too. Fixes #593 and #497. #613

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

niconoe-
Copy link
Contributor

@niconoe- niconoe- commented Feb 3, 2025

Fixes #593
Fixes #497

This is to be merged in the master branch. After taking another look, it does not seem to be a BC Break as I thought in #593, as the indexHints should just be added from the JOIN clause handling, not being removed from the SELECT statement.

I'll do another PR for the 5.10.x and 5.11.x versions, as this one uses new features from v6 the v5 doesn't have yet.

@niconoe-
Copy link
Contributor Author

niconoe- commented Feb 3, 2025

AFAIK, all mutants here are actually from previous states, so I'm not sure it's the role of this PR to try to kill em. What do you think about @williamdes ?

@williamdes
Copy link
Member

AFAIK, all mutants here are actually from previous states, so I'm not sure it's the role of this PR to try to kill em. What do you think about @williamdes ?

yeah okay, no worries then. Thank you for checking

Copy link
Member

@williamdes williamdes left a comment

Choose a reason for hiding this comment

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

This looks okay
Please add the fixes lines to the PR description

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.

Building statement with FORCE INDEX results in wrong SQL FORCE INDEX is not parsed correctly
2 participants