I am using JDeveloper 12.2.1.4 and have a filterable af:table that was throwing a java.sql.SQLException: Invalid column type error.
The db/java types for the columns/attributes are either vartchar2/string or number/Integer and the entities/views where they were defined were created with the “business components from tables wizard.”
I found I was able to resolve that error by changing the binding type. Both oracle positional and JDBC positional work and oracle named does not, so I don't really believe it is a type error.
The database is oracle 10g.
Is this perhaps a JDBC bug or an expected incompatibility with 12.2.1.4 drivers and the old 10g database?
When figuring out the workaround, I also noticed that to get the option to change the binding type, you have to uncheck "Calculate Optimized Query at Runtime (Recommended)." However, you can recheck it after changing the binding type, hiding the option, but still using the new value. I have no problem editing the view xml source directly, but at a minimum the dropdown for binding type not being available unless “Calculate Optimized Query at Runtime (Recommended)” is unchecked seems like a bug seems like JDev UI bug (or maybe being allowed to recheck it when the value is binding type is anything other than the default shouldn't be allowed?).
Digressing, I am mostly just interested in if there is any value in trying to get my Views working with the default OracleNamed parameter binding type and if needing to use oracle or jdbc positional binding styles instead instead is known or expected in some cases that I did not uncover searching support.