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

query plan hint support #183

Open
bradzacher opened this issue Aug 8, 2017 · 0 comments
Open

query plan hint support #183

bradzacher opened this issue Aug 8, 2017 · 0 comments

Comments

@bradzacher
Copy link
Contributor

It'd be good if you could add the ability to do things like mysql's FORCE INDEX / mariadb's USE INDEX hints.

There are some situations when the DB's optimiser sucks and needs a little help for a particular join.

For example, I've got a join whose conditions are well indexed, but mysql decides to ignore the index. If I wasn't using join-monster, I could rectify this issue (and reduce the query time by a factor of 5) by adding FORCE INDEX (xxx) after the table name in the join.

I know postgres doesn't have it, but something like a prefix/postfix option for joins would be good so that there is general support for doing things like this.

IIRC oracle can do this via comments in the select. This might be possible via the alwaysFetch option.

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

No branches or pull requests

2 participants