Hi,

I have been using nHibernate for a while, and follow the development mailing list, but it's my first post here.

I have a problem with proxies, which I was wondering what the "prefered" solution is.
I have a inherence structure like this:

I have interfaces for each (same inheritence structure), and set the use them for the proxys.
The classes are mapped as "joined sub classes", with a table for each (sub)type

My question is, what is the best way of establishing the type of an object loaded through the proxy? Clearly the:

construct isn't going to work as the proxy implements all the interfaces.

Any ideas would be appreciated!

Dries.

Using nHibernate 1.0.4 and MS SQLserver 2005.
Probably makes no difference though ...

Why do you have to use proxies? I would recommend turning off the proxy for these scenarios. Just because the proxy is there as a tool doesn't mean you have to use it for all objects. Use it where it makes sense, and don't use it where it doesn't make sense.

That is basically the approach we took in our application. We have a good number of inheritance trees in our application, and we have had to skip proxies for most of them.

We need to proxies for the lazy loading, otherwise in some scenarios (properties through the many-to-one side of the mapping) we end up with loooooads of SQL statements and a huge object graph when we just one a collection of objects and proxy objects on the many-to-one property as we're usually not interested in it.