The IP can be implemented with no optimization performed, but doing so results in very inefficient access to your data source. For example, if the CURVALUE table has 30,000 records, the example query would require the IP to read all 30,000 rows and to evaluate each row against the where clause. This is not necessary if the IP developer has an efficient way of accessing specific rows and making use of the optimization supported by the OpenAccess SDK SQL engine.
In the optimal case, the IP should only read the rows with NAME equal to SCOTT, TOM, and JOE, and then process them through the complete WHERE clause to reduce it to TOM and JOE due to the value constraint. The OpenAccess SDK SQL engine provides the functionality necessary to support this type of optimization.
