Preface

    If this error is reported, it must be that there is no error in the SQL, just a failure to interact with the database, so there is no need to change the code or
 to fix the logic.

Solutions

**The only thing to do is to check whether the mapping relationship between the properties of JavaBean entity fields and those in the library is OK**

Similar Posts:

• [Solved] Hibernate Error: org.hibernate.InstantiationException: No default constructor for entity
• Program error: the table or view does not exist [Solved]
• [Solved] Springboot Error: sprintgboot Unknown column ‘name’ in ‘field list’
• The model backing the ‘XXX’ context has changed [Solved]
• java.sql.SQLException: Fail to convert to internal
• nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet
• [Solved] Search with xadmin_ Related field got invalid lookup: icontains
• org.hibernate.QueryException: could not resolve property
• SpringMVC @RequestBody Error:Unrecognized field, not marked as ignorable
• Solution of data truncated for column ‘xxx’ in MySQL