Closed adrianboangiu closed 2 years ago
I'm afraid it's a limitation of ODCI that cannot be overcome. ODCITABLEDESCRIBE is called by Oracle when it first parses the query. During that step, all non-literals (except simple expressions made of literals) values are passed as NULL, that's why it cannot tell which overload to call.
The workaround is to use getCursor function instead, or use dynamic SQL.
Hello Marc,
I am using Oracle 19 and the cursor_sharing parameter is set to exact. I am trying to use ExcelTable.getRows and to specify the sheet using a function in a package. I obtain the folowing error:
If I use a hardcoded value everything works. Best regards