You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/08/09 12:32:32 UTC

[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

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

Pavel Tupitsyn updated IGNITE-2602:
-----------------------------------
    Fix Version/s:     (was: 1.7)
                   1.8

> Queries: offset does not work with negative or MAX_VALUE limit
> --------------------------------------------------------------
>
>                 Key: IGNITE-2602
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2602
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>             Fix For: 1.8
>
>
> H2 allows specifying negative LIMIT with OFFSET: http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)