[
https://issues.jboss.org/browse/TEIIDDES-2548?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-2548:
-------------------------------------------
The problem is confined to the UI in that it is the Transformation SQL Editor that
produces the incorrect SQL syntax. When the editor is saved, the sql containing \u0000 is
stored in a node tree. During the construction of this node tree, java internally
'reads' the unicode character \u0000 and converts it into its ASCII equivalent \0.
This character is referred to as the NUL character and is the traditionally used
terminator for string arrays in computer languages.
Once the node tree has been parsed, resolved and validated it is converted back to a
string for redisplay in the SQL Editor. When the string is 'printed' to the
screen, it reads the string as far as the first terminating NUL character and completes.
The remaining text, still stored in the string is not displayed. In addition, since the \0
is now part of the text, when converting to XML during the saving to the underlying XMI
file, the NUL character is converted to the XML equivalent (�).
By ensuring that the display string of the NUL character remains \u0000, this difficulty
can be avoided.
xml encoding/decoding destroys a sql query for Transformation in a
view model
------------------------------------------------------------------------------
Key: TEIIDDES-2548
URL:
https://issues.jboss.org/browse/TEIIDDES-2548
Project: Teiid Designer
Issue Type: Bug
Components: Editors
Affects Versions: 9.0.1, 9.1, 9.0.2
Environment: JBDS 8.1.0
Reporter: hisao furuichi
Assignee: Paul Richardson
Fix For: 9.0.2
In a sql query for transformation in a view model, If user writes "ESCAPE
'\u0000'" and save it, it will saved as "ESCAPE
'�'" and can not open the view model anymore with parse exception.
The reason why user wants to set "ESCAPE '\u0000' is a workaround for this
jira ticket, TEIIDDES-2217.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)