Java Mailing List Archive

http://www.gg3721.com/

Home » the NHibernate development list »

[NHibernate-development] Optional type in criteria

Ayende Rahien

2008-06-27

Replies:

Author LoginPost Reply
The introduction of EntityName has cause several issues for users of NH.
Specifically, there are several frameworks that relies on things like:

Query.Execute( DetachedCriteria.For<Foo>() );

They use the DC to get the type, from the type get the current session, etc. The problem is that without the type, you can't get the session, which doesn't leave you any option to do the "proper" resolution.
Since in many scenarios, we construct DC with type, I suggest bringing back the type name, with a name that clarify that it is optional.
Maybe something like OptionalRootClass
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nhibernate-development mailing list
Nhibernate-development@(protected)
https://lists.sourceforge.net/lists/listinfo/nhibernate-development
©2008 gg3721.com - Jax Systems, LLC, U.S.A.