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

Maksim Zhuravkov updated IGNITE-20970:
--------------------------------------
    Description: 
Let's disallow null dynamic parameters in LIMIT/OFFSET clauses.  The following 
statements should be rejected by SQL validator, because null is not valid value 
for limit / offset clause:

{code:java}
sql("SELECT * FROM t LIMIT ?", new Object[]{null});
sql("SELECT * FROM t OFFSET ?", new Object[]{null});
sql("SELECT * FROM t LIMIT ? OFFSET ?", new Object[]{null});
{code}


  was:
Let's disallow null dynamic parameters in LIMIT/OFFSET clauses.  The following 
statements should be rejected by SQL validator, because null is not valid value 
for limit / offset clause:

{code:java}
sql("SELECT * FROM t LIMIT ?", new Object{}[null]);
sql("SELECT * FROM t OFFSET ?", new Object{}[null]);
sql("SELECT * FROM t LIMIT ? OFFSET ?", new Object{}[null]);
{code}



> Sql. Disallow null dynamic parameters in LIMIT/OFFSET clauses.
> --------------------------------------------------------------
>
>                 Key: IGNITE-20970
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20970
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Priority: Minor
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Let's disallow null dynamic parameters in LIMIT/OFFSET clauses.  The 
> following statements should be rejected by SQL validator, because null is not 
> valid value for limit / offset clause:
> {code:java}
> sql("SELECT * FROM t LIMIT ?", new Object[]{null});
> sql("SELECT * FROM t OFFSET ?", new Object[]{null});
> sql("SELECT * FROM t LIMIT ? OFFSET ?", new Object[]{null});
> {code}



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

Reply via email to