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

TCK challenge against boolean result of Query #924

Conversation

njr-11
Copy link
Contributor

@njr-11 njr-11 commented Jan 6, 2025

Fixes #923 by switching the TCK test from the invalid boolean return value for @Query("UPDATE ... to instead have a return type of int. Also, improves documentation of Query to clarify what the int and long return values mean.

A separate PR/issue should be used if we decide that we also want to support a boolean return type.

@njr-11 njr-11 added bug Something isn't working test Something test-related labels Jan 6, 2025
@njr-11 njr-11 added this to the 1.1 milestone Jan 6, 2025
* <p>For {@code update} or {@code delete} statements, the return value must be one of:</p>
* <ul>
* <li>{@code void}</li>
* <li>{@code int} or {@code long}, where the value is the number of matching entities</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please only include that with a NoSQL database that works with eventual persistence; this value might not be as precise as an ACID database. Such as, a relational database.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I added that in 111205c

@otaviojava otaviojava merged commit 5dbfab1 into jakartaee:main Jan 15, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test Something test-related
Projects
None yet
3 participants