[
https://issues.jboss.org/browse/TEIID-1952?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1952:
---------------------------------------
Yes we could also use the Oracle specific type code, that removes the need for reflection.
The user would still need to set the OracleSuppliedDriver translator property flag.
I'm not sure what you mean by your second statement. The logic that determines
potential bind values is quite simplistic and is not aware of the surrounding expression -
either at the time it is marked as a bind value or at the time it is bound. Adding
initial awareness of the expression just requires tweaks to the SQLConversionVisitor,
which translators can override. But then we'd have to add quite a bit of code to
catch each scenario - comparison predicate, in predicate, like, etc. and then convey that
to the binding method on the JDBCExecutionFactory. It's much simpler to just not bind
string values. The heart of the issue is our lack of a fixed length (beyond 1) char type.
Until we add that, or at the very least have a more flexible type system that may
simplify propagation of source type information, this is not a straight-forward exercise.
Given the workarounds I don't think this merits a lot of effort.
Oracle native driver preparedstatement char parameters are required
to be padded
--------------------------------------------------------------------------------
Key: TEIID-1952
URL:
https://issues.jboss.org/browse/TEIID-1952
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 7.6
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.7.1
The ojdbc driver expects the method setFixedChar to be used to set char values regardless
of their padding. This does not occur with other drivers, such as the DataDirect Oracle
JDBC.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira