Improve resolution of parameter references used in compare criteria ------------------------------------------------------------------- Key: TEIID-188 URL: https://jira.jboss.org/browse/TEIID-188 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.x Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor 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.