We have some old code here and our client is arguing that our product cannot scale because of our implementation of NHibernate (version 1.0.1.0).
Our product has:
class A class B : A class C : A
When we:
ISession.Load(typeof(A)), 5)
The following SQL is generated:
Select …… FROM A OUTER JOIN B OUTER JOIN C WHERE A.ID = 5
They are adding new classes that inherit from A all the time and the above query is getting quite huge.
My question is twofold....
1.) Is this implementation necessary wrong (it was done a very long time ago), and 2.) What is the best way to resolve the situation going forward.
Thanks folks.
|