[
https://issues.jboss.org/browse/TEIID-4340?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4340:
---------------------------------------
but I can't seem to leverage that along with the TEXTTABLE
function to provide a usable query... any other thoughts?
Yes that will strip the BOM. Locally that seems to work fine. Are you running into
issues with files that are longer than 4000 characters?
For this issue we could extend the behavior of the UTF8 charset to include BOM handling -
which would make it consistent with java's UTF16 and 32 handling -
https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc....
add encoding as "UTF-8-BOM" in the file translator override
property
--------------------------------------------------------------------
Key: TEIID-4340
URL:
https://issues.jboss.org/browse/TEIID-4340
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.7.8.6_2
Reporter: Debbie Steigner
Priority: Trivial
Fix For: Open To Community
it will be good if teiid supports Encoding to "UTF-8-BOM" since other
middleware technologies supports similar to this and also even editor such as Notepad++
supports to convert / save file as "UTF-8-BOM".
Currently we have added Translator override for File to include "Encoding Property
to UTF-8" so similarly we should be able to set it to "UTF-8-BOM" , instead
of writing code manually to add BOM to generate a file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)