-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Use Case]: Statically specify First/Limit at dev time so that singular return type can be valid on methods #532
Comments
@njr-11 @otaviojava do you think we should scope this for 1.1? I think we should discuss it at least. |
I agree with including it. It would be easy to add and is useful. |
Reopening. TCK is still needed. |
@njr-11 I was wondering if it would be better to track the TCK work in the TCK issue, rather than leaving lots of issues open. |
1 similar comment
@njr-11 I was wondering if it would be better to track the TCK work in the TCK issue, rather than leaving lots of issues open. |
… solution to NonUniqueResultException Signed-off-by: Nathan Rauh <nathan.rauh@us.ibm.com>
That would be fine with me. It wasn't listed there, but I just added it. In the case of this particular issue, the API work wasn't actually done yet either because there is also the part in the issue description about updating the text of |
As a ...
I need to be able to ...
statically specify a limit at development time
Which enables me to ...
write a repository method with a singular return type (
Optional<MyEntity>
orMyEntity
).Additional information
This is currently only possible (and awkwardly so) with Query by Method Name.
To allow it with
@Query
and parameter based queries (@Find
), we can addFirst
(proposed by Gavin in #530 (comment))The value would default to
1
.Reminder to update recommendations in
NonUniqueResultException
once we have this.This is being proposed for after Jakarta Data version 1.0.
The text was updated successfully, but these errors were encountered: