-
Notifications
You must be signed in to change notification settings - Fork 90
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
Entity literal preferred over path in parsing when entity name and attribute names conflict #1294
Comments
Hi, this could be an issue with the |
Hi @beikov, thank you for the quick response. I will create one and get back to you. |
The problem is that the entity name of |
You could workaround the type checking issue by using the
|
@beikov, thank you for this feedback. I was troubleshooting and arrived at the same conclusion that it was being treated as a literal (even though I did not know what that meant :D) I dug a bit further into why it was being treated as a literal and found that the delate of instance After seeing this I made a change to my SchoolImpl, which removed the startup error as the duplicate within the Type resolver was gone From:
To:
At this point I assumed it was an issue with my setup but I will also try your suggestions to see the effects. |
So in JPQL/HQL there are two ways to refer to an entity. Through the FQCN and the entity name. The name you specify in |
Confirming that changing to uppercase also removed the error |
@beikov, thanks again for your help with this...really appreciate it! And thanks for a great library, wish I found it sooner! |
Spread the word ;) |
Description
Hi, I recently discovered Blaze Persistence and so far has been great at solving some issues I was having. I have arrived at a particular issue that I cant seem to find the solution for.
I am trying to use nested view for ManyToOne mapping but gets an error, this is not a bug report but more of a request for help.
Entities
Some fields removed for simplicity
Subject
School
Views
These are the complete views, nothing removed
Subject
School
Domain
Stacktrace
Whenever I try to build I get the following error
With the above error while building application I can see the following generated classes
SubjectView_
SubjectViewImpl
Environment
Version: 1.5.1
JPA-Provider: Hibernate 5.4.15.Final
DBMS: Postgres 11
Application Server: Java EE with Spring Data
If I remove
getSchool()
from the SubjectView the error goes away. Any idea what I am doing wrong or missing. I am still going through the documentations and appreciate any pointers that could help in my troubles. Hopefully the information provided is enough, thank you.The text was updated successfully, but these errors were encountered: