your other options is to go to the dev mailing list and propose a change
that you are willing to do, that would allow this function.
Not saying you will get a positive response, but it is worth a shot.
if you get a positive response they will tell you the next step.
ian tabangay sent the following on 11/20/2008 4:30 AM:
> That's not really very efficient especially if youre trying to find a few
> items from a hundred thousand. Putting it in a list would easily give you an
> OutOfMemoryException. I have a workaround for this but its done using
> SQLProcessor which could be problematic later on. Any other suggestions?
>
> On Thu, Nov 20, 2008 at 6:15 PM, Bilgin Ibryam <[EMAIL PROTECTED]> wrote:
>
>> One way could be
>>
>> values = delegator.findList("EntityName", null, null, null, null, true);
>> List field1Values = EntityUtil.getFieldListFromEntityList(values, "field1",
>> true);
>> finalValues = delegator.findList("EntityName",
>> EntityCondition.makeCondition("field2", EntityOperator.IN, field1Values),
>> null, null, null, true);
>>
>> Bilgin
>>
>>
>> On Nov 20, 2008, at 5:01 AM, ian tabangay wrote:
>>
>> i am familiar with findList and how to use EntityConditionList and
>>> EntityExpr. But i am only familiar with comparing a column with a given
>>> value (like new EntityExpr("columnName", EntityOperator.EQUALS, value).
>>> What
>>> i wanted to do is to compare 2 columns of an entity. For example, if it
>>> were
>>> written as an SQL, it would be something like "SELECT column_a, column_b
>>> FROM table WHERE column_a = column_b"
>>>
>>> On Wed, Nov 19, 2008 at 9:17 PM, BJ Freeman <[EMAIL PROTECTED]> wrote:
>>>
>>> do a search in code for findList
>
