[
https://issues.jboss.org/browse/TEIID-1530?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1530.
-----------------------------------
Resolution: Done
updated the literal matching regex. I didn't address handling postgres escaping.
That should be straightforward tough with using the teiid unescape function if the literal
begins with an E. this isn't imperative fix since it's unlike that an odbc
table/column/procedure identifier will contain a formatting character.
ODBC identifer matching issues
------------------------------
Key: TEIID-1530
URL:
https://issues.jboss.org/browse/TEIID-1530
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4
The odbc system query matching only allows literals that have basic characters. A lesser
issue is that it also does not consider postgres escaping, which changes how formating
characters are entered.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira