Hello, today we found very strange bug/behavior. When you use findByCondition with condition on field in OneToMany relation together with result transformer DISTINCT_ROOT_ENTITY and paging (limit maxRow) you get incorrect result because our code find out that you received less records than you asked for (because of result transformer) and fill pagingResult with wrong values. We resolved it for our case but I guess this need some generic care also in framework. However I don't know what to do with it. One solution will be that we will do result transformation to distinct_root_entity "by hand" in our code but you still can get strange paging result like you ask for 30 rows and you get 15 with unknown number of total rows. Or we should change default value of resultTransformer or somehow detect you are making condition through OneToMany relation and do something special. Any idea?
Pavel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
