[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327264#comment-17327264
]
Konstantin Orlov commented on IGNITE-14545:
-------------------------------------------
There is relatively easy way to support 32-bit characters too. We could provide
{{SqlOperatorTables.chain}} with our custom table first. And for string related
function we have to deal with code points, not chars. Here is how we could
derive a proper string length with regards to 32-chars: {{str.codePointCount(0,
str.length())}}. And here is snippets for substring:
{{str.substring(str.offsetByCodePoints(0, from), str.offsetByCodePoints(0, from
+ len))}}. But I don't 100% sure about this approach.
> Calcite engine. Unicode literal not supported
> ---------------------------------------------
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
> Reporter: Taras Ledkov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT <any_string_with_unicode_symbols>}}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
