Nhibernate table per hierachy and self reference table?

We use a fairly similar structure in an NH application. The differences I can see with your mapping are.

We use a fairly similar structure in an NH application. The differences I can see with your mapping are: 1) We do not nest the class definitions 2) We specify fetch='select' on the many-to-one element 3) We use lazy='true' on the bag element So reworking your mapping would look like: ... ... ... As an aside I question whether you really want to use a subclass for Manager. What happens when someone gets promoted?

Or you simply want to assign a junior subordinate? You will need to change the type of this object and probably recreate the row and update all associated records I generally only use a different class where there is fairly strong type immutability.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.