You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Ruben Q L (Jira)" <ji...@apache.org> on 2020/06/18 16:08:00 UTC

[jira] [Resolved] (CALCITE-3951) Support different string comparison based on SqlCollation

     [ https://issues.apache.org/jira/browse/CALCITE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruben Q L resolved CALCITE-3951.
--------------------------------
    Resolution: Fixed

Resolved via https://github.com/apache/calcite/commit/fa8349069d141d3c75bafa06d5fb8800711ec8d6

> Support different string comparison based on SqlCollation
> ---------------------------------------------------------
>
>                 Key: CALCITE-3951
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3951
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ruben Q L
>            Assignee: Ruben Q L
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.24.0
>
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Currently SqlCollation defines concepts like Coercibility, Charset, Locale, etc. However, we cannot specify on a certain collation that e.g. a string field should use case insensitive comparison. The goal of this ticket is to evolve SqlCollation to support that, and adapt the corresponding classes to use that (optional) "non-standard" comparison.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)