Explain the function of static keyword and final keyword in Java in detail>>>
Org.hibernate.queryexception: solutions to the error of could not resolve property
This exception is mostly due to the confusion in the use of HQL and SQL statements. Because hibernate uses HQL syntax, and SQL syntax is different from it. Of course, if the fields added to the table are the same as those mapped to attribute fields in the HBM. XML file, this rarely happens
for example, if Id is a field of a table, then it is also an ID in the hbm.xml file, so there should be no problem when searching. However, the field added to my table is person_ Name, then it may be personname in hbm.xml file, so you should pay attention when using fields, otherwise, org.hibernate.queryexception: could not resolve will appear
Note: fields in HQL are consistent with field attributes in entity class
Similar Posts:
- Solution of data truncated for column ‘xxx’ in MySQL
- [Solved] Object references an unsaved transient instance – save the transient instance before flushing
- Springmvc Error: HTTP Status 500 – Could not write content: No serializer
- [Solved] Search with xadmin_ Related field got invalid lookup: icontains
- [Solved] MySQL Add New Field Error: ERROR 1118 — Row size too large. The maximum row size for the used table type
- [Solved] org.hibernate.hql.internal.ast.QuerySyntaxException: persons is not mapped…
- [Solved] org.hibernate.hql.internal.ast.QuerySyntaxException: persons is not mapped…
- [Solved] Hibernate Error: org.hibernate.InstantiationException: No default constructor for entity
- [Solved] org.hibernate.AnnotationException: No identifier specified for entity: com.example1.demo1.Entity….
- [Solved] Elasticsearch:exception [type=search_phase_execution_exception, reason=all shards failed]