Databases
StackOverflow2013
Postsdbo
POnhibernate upgrade 2.1 to 3.3, exception when using DistinctRootEntityResultTransformer
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POnhibernate upgrade 2.1 to 3.3, exception when using DistinctRootEntityResultTransformer
    text
    copied!<p>We've upgraded NHibernate from 2.xx to 3.3. It works well but we have some usages of </p> <pre><code>SetResultTransformer(new DistinctRootEntityResultTransformer()) </code></pre> <p>And now we get "Index was outside the bounds of the array" exception when doing </p> <pre><code>.List&lt;Entity&gt;() </code></pre> <p>The Stack trace shows that the error comes from <code> at NHibernate.Type.TypeHelper.Disassemble(Object[] row, ICacheAssembler[] types, Boolean[] nonCacheable, ISessionImplementor session, Object owner) at NHibernate.Cache.StandardQueryCache.Put(QueryKey key, ICacheAssembler[] returnTypes, IList result, Boolean isNaturalKeyLookup, ISessionImplementor session) at NHibernate.Loader.Loader.PutResultInQueryCache(ISessionImplementor session, QueryParameters queryParameters, IType[] resultTypes, IQueryCache queryCache, QueryKey key, IList result) at NHibernate.Loader.Loader.ListUsingQueryCache(ISessionImplementor session, QueryParameters queryParameters, ISet<code>1 querySpaces, IType[] resultTypes) at NHibernate.Loader.Loader.List(ISessionImplementor session, QueryParameters queryParameters, ISet</code>1 querySpaces, IType[] resultTypes) at NHibernate.Loader.Criteria.CriteriaLoader.List(ISessionImplementor session) at NHibernate.Impl.SessionImpl.List(CriteriaImpl criteria, IList results) </code></p> <p>Any clues?</p> <p>I found this: <a href="https://nhibernate.jira.com/browse/NH-2961" rel="nofollow">https://nhibernate.jira.com/browse/NH-2961</a></p> <p>And if you remove, fetchmode.join or distinctrootentitytransformer or cache, it works.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload