[
https://jira.jboss.org/jira/browse/TEIID-188?page=com.atlassian.jira.plug...
]
Ramesh Reddy updated TEIID-188:
-------------------------------
Component/s: Query Engine
Fix Version/s: 6.x
Affects Version/s: 6.x
Improve resolution of parameter references used in compare criteria
-------------------------------------------------------------------
Key: TEIID-188
URL:
https://jira.jboss.org/jira/browse/TEIID-188
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.x
Reporter: Mark Drilling
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.x
Attachments: GregComments.txt
Original Estimate: 1 day
Remaining Estimate: 1 day
Entering this JIRA from Issue 185605 in issue tracker. Greg Haber reports problem using
Penrose off the shelf application. Example query as follows
select distinct petOwnersFromMM.owner, petOwnersFromMM.name from
petVirtualDB.gregtest_virtual.gregtest.pet petOwnersFromMM where
lower(petOwnersFromMM.owner) = lower(?) order by petOwnersFromMM.owner
He is getting "com.metamatrix.jdbc.MMSQLException: The function 'lower(?)'
has more than one possible signature." since the lower function is ambiguous.
Workaround is to use "lower(convert(?, string))" in the sql. There is a
statement in the release notes for a future enhancement that we could use the type info
from the other side of the compare criteria to determine what the type should be.
I will attach Gregs further comments for reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira