findservices.java (excecuteFind)

[BJ Freeman]

this is more a question.
notice that the EntityFindOptions call has two options hard set, like
the use distinct set to false, instead of passing the parm.

wouldn't it override higher level calls.

       // Retrieve entities  - an iterator over all the values
         EntityListIterator listIt = null;
         try {
             if (noConditionFind || (entityConditionList != null &&
entityConditionList.getConditionListSize() > 0)) {
                 listIt =
delegator.findListIteratorByCondition(entityName, entityConditionList,
                         null, null, orderByList, new
EntityFindOptions(true, EntityFindOptions.TYPE_SCROLL_INSENSITIVE,
EntityFindOptions.CONCUR_READ_ONLY, false));
             }
         } catch (GenericEntityException e) {
             return ServiceUtil.returnError("Error running Find on the
[" + entityName + "] entity: " + e.getMessage());
         }

[Ruth Hoffman]

Hi BJ:
Yes I tried turning those on and off - when I set the
TYPE_SCROLL_INSENSITIVE to true, I get the timeout/out of memory errors.
When I set it to false, I can retrieve 100 or so records and iterate
through them, but I can't get anymore records from that result set.
CONCUR_READ_ONLY doesn't seem to make a bit of difference as far as the
timeout problems are concerned.

Ruth

BJ Freeman wrote:

> this is more a question.
> notice that the EntityFindOptions call has two options hard set, like
> the use distinct set to false, instead of passing the parm.
>
> wouldn't it override higher level calls.
>
>       // Retrieve entities  - an iterator over all the values
>         EntityListIterator listIt = null;
>         try {
>             if (noConditionFind || (entityConditionList != null &&
> entityConditionList.getConditionListSize() > 0)) {
>                 listIt =
> delegator.findListIteratorByCondition(entityName, entityConditionList,
>                         null, null, orderByList, new
> EntityFindOptions(true, EntityFindOptions.TYPE_SCROLL_INSENSITIVE,
> EntityFindOptions.CONCUR_READ_ONLY, false));
>             }
>         } catch (GenericEntityException e) {
>             return ServiceUtil.returnError("Error running Find on the
> [" + entityName + "] entity: " + e.getMessage());
>         }
>

[BJ Freeman]

I think you were answering the other email thread.
this is a service, that I believe answers why setting the distinct true
has no effect.


Ruth Hoffman sent the following on 8/1/2006 11:24 AM:

> Hi BJ:
> Yes I tried turning those on and off - when I set the
> TYPE_SCROLL_INSENSITIVE to true, I get the timeout/out of memory errors.
> When I set it to false, I can retrieve 100 or so records and iterate
> through them, but I can't get anymore records from that result set.
> CONCUR_READ_ONLY doesn't seem to make a bit of difference as far as the
> timeout problems are concerned.
>
> Ruth
>
> BJ Freeman wrote:
>
>> this is more a question.
>> notice that the EntityFindOptions call has two options hard set, like
>> the use distinct set to false, instead of passing the parm.
>>
>> wouldn't it override higher level calls.
>>
>>       // Retrieve entities  - an iterator over all the values
>>         EntityListIterator listIt = null;
>>         try {
>>             if (noConditionFind || (entityConditionList != null &&
>> entityConditionList.getConditionListSize() > 0)) {
>>                 listIt =
>> delegator.findListIteratorByCondition(entityName, entityConditionList,
>>                         null, null, orderByList, new
>> EntityFindOptions(true, EntityFindOptions.TYPE_SCROLL_INSENSITIVE,
>> EntityFindOptions.CONCUR_READ_ONLY, false));
>>             }
>>         } catch (GenericEntityException e) {
>>             return ServiceUtil.returnError("Error running Find on the
>> [" + entityName + "] entity: " + e.getMessage());
>>         }
>>
>

[Ruth Hoffman]

Hi BJ:
Yes, you are correct.
Sorry.
Ruth

BJ Freeman wrote:

> I think you were answering the other email thread.
> this is a service, that I believe answers why setting the distinct
> true has no effect.
>
>
> Ruth Hoffman sent the following on 8/1/2006 11:24 AM:
>
>> Hi BJ:
>> Yes I tried turning those on and off - when I set the
>> TYPE_SCROLL_INSENSITIVE to true, I get the timeout/out of memory
>> errors. When I set it to false, I can retrieve 100 or so records and
>> iterate through them, but I can't get anymore records from that
>> result set. CONCUR_READ_ONLY doesn't seem to make a bit of difference
>> as far as the timeout problems are concerned.
>>
>> Ruth
>>
>> BJ Freeman wrote:
>>
>>> this is more a question.
>>> notice that the EntityFindOptions call has two options hard set,
>>> like the use distinct set to false, instead of passing the parm.
>>>
>>> wouldn't it override higher level calls.
>>>
>>>       // Retrieve entities  - an iterator over all the values
>>>         EntityListIterator listIt = null;
>>>         try {
>>>             if (noConditionFind || (entityConditionList != null &&
>>> entityConditionList.getConditionListSize() > 0)) {
>>>                 listIt =
>>> delegator.findListIteratorByCondition(entityName, entityConditionList,
>>>                         null, null, orderByList, new
>>> EntityFindOptions(true, EntityFindOptions.TYPE_SCROLL_INSENSITIVE,
>>> EntityFindOptions.CONCUR_READ_ONLY, false));
>>>             }
>>>         } catch (GenericEntityException e) {
>>>             return ServiceUtil.returnError("Error running Find on
>>> the [" + entityName + "] entity: " + e.getMessage());
>>>         }
>>>
>>
>