The native postgresql still uses the convert layer for two keywords: SYSDATE -> converted to getDate() LIKE -> converted to SIMILAR TO when the user preference is set
This leads to errors because the replacement is conducted in the whole SQL string, even within quoted strings.
Test case example:
Login with System role
Window Reference
Push the Find button
Fill Name with %sysdate% (this is to search any reference with sysdate in the name)
Oracle and postgres return one record with name "C_Period - all, acct, sysdate, desc"
Native postgres doesn't return any record - because the sysdate is converted to getdate()
The native postgresql still uses the convert layer for two keywords:
SYSDATE -> converted to getDate()
LIKE -> converted to SIMILAR TO when the user preference is set
This leads to errors because the replacement is conducted in the whole SQL string, even within quoted strings.
Test case example:
Login with System role
Window Reference
Push the Find button
Fill Name with %sysdate% (this is to search any reference with sysdate in the name)
Oracle and postgres return one record with name "C_Period - all, acct, sysdate, desc"
Native postgres doesn't return any record - because the sysdate is converted to getdate()