How to solve @ Column mapping inconsistency

This article mainly introduces "how to solve @ Column mapping inconsistencies". In daily operation, I believe many people have doubts about how to solve @ Column mapping inconsistencies. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "how to solve @ Column mapping inconsistencies"! Next, please follow the editor to study!

@ Column mapping inconsistency repeats @ Column (name = "userName", nullable = true, length = 20) private String userName

But the table field generated in mysql is user_name

Solution jpa: hibernate: ddl-auto: update naming: physical-strategy: org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl show-sql: true

Mainly set the physical-strategy property

In addition, the self-increasing method of mysql primary key

@ Id @ GeneratedValue (strategy = GenerationType.IDENTITY) @ Column annotation mapping does not take effect

@ Column is inexplicably invalid in mybatis-plus. You can use @ TableField instead.

Note that the value of tableField should be exactly the same as the database table name (hump to hump, underscore to underscore)

At this point, the study on "how to solve @ Column mapping inconsistencies" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!