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.

Sign up for GitHub

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

Jump to bottom

fix TQRootBean.exists() when used with .or() #3308

Merged
merged 2 commits into from
Jan 18, 2024
Merged

fix TQRootBean.exists() when used with .or() #3308

merged 2 commits into from
Jan 18, 2024

Conversation

Incanus3
Copy link
Contributor

No description provided.

@rbygrave rbygrave added this to the 13.25.3 milestone Jan 18, 2024
@rbygrave rbygrave added the bug label Jan 18, 2024
@rbygrave
Adjust test such that table alias does not clash
0046d98 
The .raw("contact.customer_id = customer.id") clashes as "customer.id" is
a logical path from contact
@rbygrave
Copy link
Member

Great work. I've just adjusted that test there because we had a clash with .raw("contact.customer_id = customer.id") in that customer.id is a valid logical path from Contact (the ManyToOne to customer). So changing the alias so that it didn't clash there.

@rbygrave rbygrave linked an issue Jan 18, 2024 that may be closed by this pull request
Wrong junction generated when using OR with EXISTS subquries #3305
Closed
@rbygrave rbygrave merged commit 2a62d41 into ebean-orm:master Jan 18, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@Incanus3 Incanus3

Labels
bug
Projects
None yet
Milestone
13.26.0
Development

Successfully merging this pull request may close these issues.

Wrong junction generated when using OR with EXISTS subquries
2 participants
@Incanus3 @rbygrave