It might be easier to patch NH to support it, then.

On Tue, Apr 13, 2010 at 8:18 AM, Peter Smulovics
<[email protected]>wrote:

> I looked at the execution plan, if I'm using 'union', than MS SQL
> server optimized the execution by chosing the appropriate branches,
> and not evaluating those that would fall out in the last order+query.
>
> Peter
>
> On 2010-04-13, Ayende Rahien <[email protected]> wrote:
> > Hundreds of queries are going to kill performance, no matter how you are
> > going to do it
> >
> > On Mon, Apr 12, 2010 at 9:45 PM, Peter Smulovics
> > <[email protected]>wrote:
> >
> >> Since that I tried everything from creating a new Junction type to
> native
> >> sql, none of them worked. Now I'm sticking with running multicriteria,
> and
> >> executing plenty of queries... which kills performance.
> >>
> >>
> >> On Wed, Apr 7, 2010 at 21:31, Ayende Rahien <[email protected]> wrote:
> >>
> >>> Can't you use a disjunction?
> >>>
> >>>
> >>> On Wed, Apr 7, 2010 at 10:05 PM, Peter Smulovics <
> >>> [email protected]> wrote:
> >>>
> >>>> hi!
> >>>>
> >>>> I have a case when I have hundreds of criterias, all of them quering
> >>>> the same type, each of them returning the top 1 result depending on
> >>>> various orders and where qualificants. What I need is the ability to
> >>>> create one huge criteria from them, returning only the top 1 row from
> >>>> their results' union again depending on various orders and where
> >>>> qualificants. I know that criterias don't support subcriteria union
> >>>> now - but is this on the roadmap? if not, do you think it can be done
> >>>> easily? I was thinking about that this differs from criteria junction,
> >>>> but similar to some of the property projections with subqueries...
> >>>>
> >>>> Peter
> >>>>
> >>>
> >>>
> >>
> >
> >
> > --
> > To unsubscribe, reply using "remove me" as the subject.
> >
>

Reply via email to