[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1620) Fetch keyword not handled

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-1620.
-----------------------------------

      Assignee: Steven Hawkins
    Resolution: Done


Added support for the offset/fetch clauses.  The default representation at this point will still be as a LIMIT clause (this means that in Designer entering a fetch clause will be shown as a limit clause).

This required adding OFFSET as a reserved word.

> Fetch keyword not handled
> -------------------------
>
>                 Key: TEIID-1620
>                 URL: https://issues.jboss.org/browse/TEIID-1620
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>         Environment: JBDS 4.0
>            Reporter: Joel Tosi
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 7.5
>
>
> Try to limit your query using native SQL construct fetch.  While there are other ways to do this inside designer, support the native SQL construct for ease of use by data architects:
> select * from SAMPLE_DATABASE fetch first 100 rows only
> jBoss Designer error:
> select * from SAMPLE_DATABASE fetch first 100 rows only
> Remote org.teiid.api.exception.query.QueryParserException: Parsing error:
> Encountered "fetch" at line 1, column 36.
> Was expecting one of:
>     <EOF>
>     "group" ...
>     "having" ...
>     "intersect" ...
>     "limit" ...
>     "makedep" ...
>     "makenotdep" ...
>     "order" ...
>     "where" ...
>     "," ...
>     ";" ...
>     "union" ...
>     "except" ...
>     "option" ...
>     "cross" ...
>     "right" ...
>     "left" ...
>     "full" ...
>     "inner" ...
>     "join" ...
> Elapsed Time:  0 hr, 0 min, 0 sec, 0 ms.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira