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

Querrying empty table for non-standard JPA type results in IllegalStateExcepion with the message "No aliases found in result tuple" [DATAJPA-1024] #1370

Closed
spring-projects-issues opened this issue Dec 13, 2016 · 2 comments
Assignees
Labels
in: core Issues in core support type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link

spring-projects-issues commented Dec 13, 2016

Pál Hebők opened DATAJPA-1024 and commented

Related to DATAJPA-984. Querrying empty table for non-standard JPA type results in IllegalStateExcepion with the message "No aliases found in result tuple", instead of returning null.
In the linked git repository this is showcased with org.joda.time.LocalDate instances. Querries for standard types, e.g. java.time.LocalDate return null as expected. It would be nice if the behaviour was unified


Affects: 1.10.5 (Hopper SR5)

Reference URL: https://github.com/PaulDaPigeon/PossibleSpringDataBug

Backported to: 1.10.6 (Hopper SR6), 1.9.7 (Gosling SR7)

@spring-projects-issues
Copy link
Author

spring-projects-issues commented Dec 13, 2016

Oliver Drotbohm commented

That's in place. I verified your sample working with the latest snapshots

@spring-projects-issues
Copy link
Author

spring-projects-issues commented Dec 13, 2016

Pál Hebők commented

Just ran the tests with the 1.10.6.BUILD-SNAPSHOT and everything looks OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core support type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants