[
https://issues.jboss.org/browse/TEIID-5709?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5709.
-----------------------------------
Resolution: Done
Updated XML name escaping, translate, and initcap to be aware of high/low pairs.
Added doc notes that the character type and places where single characters are expected,
such as trim, textagg, texttable, and like escape, are restricted to 16 bit characters.
Added a doc note that ascii and chr assume 16 bit characters and have no consistency
beyond the 255 code point for pushodwn.
I could not find an instance where our handling of object names was adversely affected as
the logic - we may quote an identifier a little aggressively but that's it.
Consistent character handling beyond bmp
----------------------------------------
Key: TEIID-5709
URL:
https://issues.jboss.org/browse/TEIID-5709
Project: Teiid
Issue Type: Bug
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
There are many places in the code that only consider each 16 bit character when we should
consult the full code point.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)