[hibernate-dev] HSEARCH-615 Support time-constrained queries returning the first available results
Sanne Grinovero
sanne at hibernate.org
Wed Dec 8 06:26:07 EST 2010
I have no strong opinions on this;
I like both
setTimeout(long timeout, TimeUnit timeUnit, boolean allowPartialResults)
and
limitExecutionTimeTo (or boundExecutionTimeTo)
The latter is only taken a milliseconds/long or is it also having a
TimeUnit parameter
but neither express clearly what's happening to my results.
limitResultCollectionTimeTo( milliseconds ) ?
(imho we can avoid the TimeUnit)
-- Sanne
2010/12/8 Hardy Ferentschik <hibernate at ferentschik.de>:
> On Wed, 08 Dec 2010 11:40:57 +0100, Emmanuel Bernard
> <emmanuel at hibernate.org> wrote:
>
>> limitExecutionTimeTo (or boundExecutionTimeTo) seems exactly what we are
>> looking for.
>>
>> WDYT?
>
> I find it a little confusing to have setTimeout and limitFetchingTime (or
> be it limitExecutionTimeTo).
> Why not having another version of setTimeout - setTimeout(long timeout,
> TimeUnit timeUnit, boolean allowPartialResults)?
>
> --Hardy
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
More information about the hibernate-dev
mailing list