[
https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2858:
---------------------------------------
I still don't think we're on the same page. You'll need to be quite explicit
as to what is happening. If you have a char[x] modeled as string, there should be no
convert involved. Can you provide a scenario where this is happening?
Yes, Tom that is understood. As an aside we do now have limited support for function
based indexes on internal materialized views.
Database use of char[>1] cause using Convert(x,x) and negates
using an index
----------------------------------------------------------------------------
Key: TEIID-2858
URL:
https://issues.jboss.org/browse/TEIID-2858
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
When a database defines a char of length greater than 1, a convert(x,x) is being used in
the criteria, and thereby, negating the use of an index and causing table scans.
Note: There is no option to change the database schemas, because they are from a COTS
product.
I would think there needs to be a solution in the translator such that if it can be
detected that its for a char column and that it does not do the convert.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira