Right, the warning is somewhat irrelevant - I'm attempting to compare
a field to another field, not a value - I was just wondering if there
was a nicer way to do it.
On Apr 13, 2009, at 5:38 PM, Adrian Crum wrote:
It is saying that one of your operator data types doesn't match the
database data type. Make sure you're comparing a BigDecimal to a
BigDecimal.
-Adrian
Joe Eckard wrote:
What is the correct way to create a "having" condition that
compares two fields? For example:
HAVING available_to_promise_total <= minimum_stock ;
I can use:
havingCondition =
EntityCondition.makeCondition('availableToPromiseTotal',
EntityOperator.LESS_THAN_EQUAL_TO,
EntityFieldValue.makeFieldValue('minimumStock'));
which works, but I get the following warning:
=-=-=-=-=-=-=-=-= Database type warning in EntityExpr =-=-=-=-=-=-=-
=-=
In entity field
[ProductFacilityLocationQuantityTest.availableToPromiseTotal] set
the value passed in [org.ofbiz.entity.condition.EntityFieldValue]
is not compatible with the Java type of the field
[java.math.BigDecimal]
Is there a cleaner way to do this type of thing that I am
overlooking?
-Joe
