Given the following tables:

User
----------
userId (PK)
userName
roleId (FK)

Role
----------
roleId (PK)
roleName

When using middlegen, I found that it generates the following classes:

User
----------
long userId
String userName
Role role

Role
----------
long roleId
String roleName
Set users

Is there a reason why the "Role" class maintains a Set of users or is this an unnecessary artifact from code generation (Read: can I delete it?)? Role is simply a look up table. I don't see the need to keep a reference back to every user. Does Hibernate use this for caching?

Regards,

Joshua

I doubt hibernate would need that for caching.
In my eyes this is an absolutley correct behaviour as you might want to view all the users that have a certain role.

I tend to agree.

Any comments from the Hibernate team?

You can have that either bidirectional or uni-directional, what you see is just a default.

Middlegen shows (in the GUI) if the relationship is uni- or bi-directional. You can change it if you want it to go only one direction. The default is to make it bi-directional.