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

Potentially breaking change: Throw PersistenceException for unknown property in select clause #3499

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

rbygrave
Copy link
Member

The prior behaviour was "relaxed" / "loose" in that it allowed unknown properties in the select clause to be ignored.

At this stage, I think this was likely to be bad behaviour in that it might not be expected and people might be thinking that the select clause is successfully including a property that in fact was getting ignored.

If you have an application that hits this PersistenceException("Property not found - ___") exception and you don't like this change in behaviour, please get in touch and lets see. In theory this change should make the behaviour better but there might be code out there that is based on the assumption that the select clause is "relaxed" wrt unknown properties.

@rbygrave rbygrave self-assigned this Oct 18, 2024
@rbygrave rbygrave added this to the 14.8.0 milestone Oct 18, 2024
@rbygrave rbygrave merged commit 423d906 into master Oct 18, 2024
1 check passed
@rbygrave rbygrave deleted the feature/3489 branch October 18, 2024 06:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NullPointerException: Cannot invoke "io.ebeaninternal.server.query.STreeProperty.name()"
1 participant