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

How to get bun to really use "INNER JOIN" instead of "LEFT JOIN". #477

Open
oderwat opened this issue Mar 5, 2022 · 3 comments
Open

How to get bun to really use "INNER JOIN" instead of "LEFT JOIN". #477

oderwat opened this issue Mar 5, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@oderwat
Copy link

oderwat commented Mar 5, 2022

I am evaluating bun for usage in one of my projects with an existing (MariaDB) database.

From the documentation I got this example:

image

It says it would use INNER JOIN instead of LEFT JOIN but It just uses LEFT JOIN with the IS NOT NULL clause. It will give the correct results but is it really expected to do it. If yes, I think the wording in the documentation needs to be "To simulate INNER JOIN instead of LEFT JOIN".

I also would like if I can force it to use INNER JOIN, especially if there is always a relation enforced in the database and everything else would be an error.

@vmihailenco
Copy link
Member

If yes, I think the wording in the documentation needs to be "To simulate INNER JOIN instead of LEFT JOIN".

Your understanding is correct - I will update the docs.

I also would like if I can force it to use INNER JOIN

There is currently no way to do that. We discussed this previously, but could not find a nice way to support this.

@vmihailenco vmihailenco added the enhancement New feature or request label Mar 30, 2022
Copy link

github-actions bot commented Nov 7, 2024

This issue has been automatically marked as stale because it has not had activity in the last 30 days. If there is no update within the next 7 days, this issue will be closed.

@github-actions github-actions bot added the stale label Nov 7, 2024
@j2gg0s j2gg0s closed this as completed Jan 3, 2025
@j2gg0s j2gg0s closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2025
@oderwat
Copy link
Author

oderwat commented Jan 3, 2025

This is pretty sad. We needed to write a lot of code manually in the last two years. This is missing and IMHO huge performance killer. Time to move on.

@j2gg0s j2gg0s reopened this Jan 3, 2025
@j2gg0s j2gg0s removed the stale label Jan 3, 2025
@j2gg0s j2gg0s self-assigned this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants