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

A way to specify join type. #11383

Open
2 of 6 tasks
sarangnx opened this issue Sep 4, 2019 · 2 comments
Open
2 of 6 tasks

A way to specify join type. #11383

sarangnx opened this issue Sep 4, 2019 · 2 comments
Labels
status: understood For issues. Applied when the issue is understood / reproducible. type: feature For issues and PRs. For new features. Never breaking changes.

Comments

@sarangnx
Copy link

sarangnx commented Sep 4, 2019

Issue Description

Is your feature request related to a problem? Please describe.

I'd like to have an option to specify full outer join rather than left outer join in includes

Describe the solution you'd like

Something like this would be nice to have:

Team.findAll({
    include: [{
        model: Players,
        join: 'FULL OUTER'   // <--- a way to specify join type.
    }]
})

Describe alternatives/workarounds you've considered

The only workaround/alternative I have found is to write raw queries.

Issue Checklist

Is this issue dialect-specific?

  • No. This issue is relevant to Sequelize as a whole.
  • Yes. This issue only applies to the following dialect(s): XXX, YYY, ZZZ

Would you be willing to resolve this issue by submitting a Pull Request?

  • Yes, I have the time and I know how to start.
  • Yes, I have the time but I don't know how to start, I would need guidance.
  • No, I don't have the time, although I believe I could do it if I had the time...
  • No, I don't have the time and I wouldn't even know how to start.
@papb papb added status: understood For issues. Applied when the issue is understood / reproducible. type: feature For issues and PRs. For new features. Never breaking changes. labels Sep 4, 2019
@papb
Copy link
Member

papb commented Sep 4, 2019

Thanks for the report, I am also not aware of a better workaround than raw queries for now. If someone else knows a better workaround, please share!

@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2021

This issue has been automatically marked as stale because it has been open for 7 days without activity. It will be closed if no further activity occurs. If this is still an issue, just leave a comment or remove the "stale" label. 🙂

@github-actions github-actions bot added the stale label Nov 7, 2021
@WikiRik WikiRik removed the stale label Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: understood For issues. Applied when the issue is understood / reproducible. type: feature For issues and PRs. For new features. Never breaking changes.
Projects
Development

No branches or pull requests

3 participants