Hi All.
Outsystems 10. JAVA EE.
I don't understand why the aggregate assigns additional filtering conditions to fields, and I can't influence this in any way.
Example:
In aggregate filter Outsystems side: entity1.field1 = "some value".
In Oracle side: SELECT .... WHERE ((entity1.field1 = "some value") AND entity1.field1 IS NOT NULL)
Why entity1.field1 IS NOT NULL?????
Who came up with this, for what purpose, and how to disable it?
Hi Sergey,
May I kindly ask, if the entity resides to the default db of the Outsystems platform or is from an external oracle db?
Thank you and regards,
Chris
Hi Christopher.
The entity resides to the default db of the Outsystems platform.
The problem is that the field has an index, but because of the predicate IS NOT NULL, the Oracle is forced to do a full scan table.