I ran into the same issue while mapping a legacy database whose structure I cannot change with Hibernate 5.4. Before stumbling upon this issue, I debugged the code and arrived at the same conclusion as Matthew Jacobs. If mapping is non-insertable and non-updatable, there does not seem to be a reason to throw an error. Would be great if this can be considered for change in the next releases.