Hibernate view processing

Closed development ......

Zibo is a good place, and Wolong Villa is very cool.

There are still a lot of problems encountered during development, and many of them are very detailed. Now let's take a look:

There is a problem with hibernate processing views:

Problem description: because the view does not have a primary key, all attributes are treated as the joint primary key during Reverse Engineering of myeclipse, which leads to a problem when querying attributes, the size in the result set is numeric, such as 1 or 2, but the objects in the result set are empty.

Solution: Move all attributes in the Union primary key class back to the primary pojo class and only keep the real Union primary key. If only one field is used as the primary key, then all attributes are removed and the Union primary key class is deleted.

Summary: there is a problem with all fields performing the Union primary key. If you need to join the primary key, you only need to put the attributes required by the Union primary key in the class corresponding to the Union primary key.