-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Reorder documentation of class-based projection support for JPA Native Queries #3599
Comments
You find the specifics at the end of the document:
This section comes below Dynamic Projections |
Okay, thanks, found it, but nevertheless, I would expect this restriction under class based projection section, not under dynamic projection (to me seems to be far more decent), and honestly, it's not the first time we encounter this issue and according to Stack Overflow discussion, we're not alone. Any plans to implement this? Should be technically possible since Spring Data JDBC has no problem with class based projections. |
…e Queries. Closes #3599
…e Queries. Closes #3599
I reordered the documentation to find the limitation much earlier. |
I've created a demo project to demonstrate the problem. It seems that only interface based projections are working fine, but if we want to use class based projections, we have the
ConverterNotFoundException
problem. Related Stack Overflow thread.It is expected that the Class Based Projections would work for native queries, as stated in the doc. Well, the doc does not mention specifically that Class Based Projections would work for native queries, but on the contrary it does not mention for what queries it would work, so the assumption is that for all
@Query
methods.The text was updated successfully, but these errors were encountered: