[
https://issues.apache.org/jira/browse/IGNITE-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625149#comment-17625149
]
Andrey Khitrin commented on IGNITE-17997:
-----------------------------------------
Thank you. I've forgot about collations. As I can see, the same behavior could
be achieved in other database engines, depending on data type and/or query
options. E.g., in [sqlite3|https://www.sqlite.org/datatype3.html#collation]:
{code:sql}
sqlite> SELECT 'a' = 'a ';
0 -- false
sqlite> SELECT 'a' = 'a ' COLLATE RTRIM;
1 -- true
{code}
In that case, I hardly can treat this behavior as a bug. At most, it's a
different default, not obvious though.
[~korlov] what would you say about IGNITE-17996? Does this behavior obey the
same rules?
Also, are there plans to support different collation schemes in the future?
> Whitespaces at the end are ignored during string comparison
> -----------------------------------------------------------
>
> Key: IGNITE-17997
> URL: https://issues.apache.org/jira/browse/IGNITE-17997
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Andrey Khitrin
> Priority: Major
>
> In 3.0.0-Beta-1:
> {code:java}
> sql-cli> select 'a' = 'a' as t1, 'a' = 'b' as t2, 'a' = 'a ' as t3, 'a' = '
> a' as t4;
> ╔══════╤═══════╤══════╤═══════╗
> ║ T1 │ T2 │ T3 │ T4 ║
> ╠══════╪═══════╪══════╪═══════╣
> ║ true │ false │ true │ false ║
> ╚══════╧═══════╧══════╧═══════╝
> {code}
> Tests T1, T2, and T4 show correct behavior. But in test T2 we see that string
> 'a' is considered being equal to string 'a ' (same string but with
> arbitrary amount of whitespaces at the end). This is incorrect behavior.
> This issue may have the same nature as IGNITE-17996, but it's just a
> hypothesis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
