PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Force Search SQL to use Bind Variables?

edited Aug 8, 2018 5:09AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 1 commentAnswered

Is there any way via App Designer to force the component's Search SQL to use Bind variables?   I.e. a Record.Field option (Key, Search Key, etc) combination that the component processor would use to alter the SQL used against the db (Oracle).   Is the field type of 'Character' causing this?

For example; if users searches on National ID, my Search View is using SQL similar to: "WHERE UPPER(NATIONAL_ID) LIKE UPPER('12345678') || '%' ESCAPE '\'

I am trying to get it to use: "WHERE UPPER(NATIONAL_ID) LIKE UPPER(:1) || '%' ESCAPE '\'"

Having performance issues that seems to be resolved if we use Bind Variables instead of SQL String -  as tested using SQL Developer.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center