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

Kirill Tkalenko updated IGNITE-27837:
-------------------------------------
    Description: 
I discovered the following issue when using  
{*}org.apache.ignite.cache.query.annotations.QuerySqlTableFunction{*}.
If we declare "columnNames = \{"age", "NAME"}," then in subsequent queries, 
"age" will be case-sensitive, but "NAME" will not.

For example, queries like these will return errors about an unknown column:
 * select * from PUBLIC.PERSON where age >= 18;
 * select * from PUBLIC.PERSON where AGE >= 18;

An example where everything works fine:
 * select * from PUBLIC.PERSON where "age" >= 18;
 * select * from PUBLIC.PERSON where name = 'Homer';
 * select * from PUBLIC.PERSON where NAME = 'Homer';

  was:
I discovered the following issue when using  
{*}org.apache.ignite.cache.query.annotations.QuerySqlTableFunction{*}.
If we declare "123= {}," then in subsequent queries, "123" will be 
case-sensitive, but "123" will not.

For example, queries like these will return errors about an unknown column:
An example where everything works fine:


> Fix handling of columnNames in QuerySqlTableFunction
> ----------------------------------------------------
>
>                 Key: IGNITE-27837
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27837
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.17
>            Reporter: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-2
>
> I discovered the following issue when using  
> {*}org.apache.ignite.cache.query.annotations.QuerySqlTableFunction{*}.
> If we declare "columnNames = \{"age", "NAME"}," then in subsequent queries, 
> "age" will be case-sensitive, but "NAME" will not.
> For example, queries like these will return errors about an unknown column:
>  * select * from PUBLIC.PERSON where age >= 18;
>  * select * from PUBLIC.PERSON where AGE >= 18;
> An example where everything works fine:
>  * select * from PUBLIC.PERSON where "age" >= 18;
>  * select * from PUBLIC.PERSON where name = 'Homer';
>  * select * from PUBLIC.PERSON where NAME = 'Homer';



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to