[teiid-issues] [JBoss JIRA] Moved: (TEIID-399) Oracle Spatial SQL translator drops the LIMIT clause.

[Steven Hawkins (JIRA)]

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

Steven Hawkins moved JBEDSP-966 to TEIID-399:
---------------------------------------------

              Project: Teiid  (was: JBoss Enterprise Data Services Platform)
                  Key: TEIID-399  (was: JBEDSP-966)
          Component/s: Misc. Connectors
                           (was: Connectors)
    Affects Version/s: 6.0.0
                           (was: 5.5.2)
                           (was: 5.5.3)
                           (was: 5.5.1)


> Oracle Spatial SQL translator drops the LIMIT clause.
> -----------------------------------------------------
>
>                 Key: TEIID-399
>                 URL: https://jira.jboss.org/jira/browse/TEIID-399
>             Project: Teiid
>          Issue Type: Bug
>          Components: Misc. Connectors
>    Affects Versions: 6.0.0
>            Reporter: John Doyle
>            Assignee: John Doyle
>
> The LIMIT SQL clause is not having an effect on our SQL queries.  In our case, we are using the Oracle Spatial connector which interfaces with an Oracle 10g database.  What configuration or connector changes are needed so we can leverage the LIMIT clause for controlling the fetch size of our result sets which are derived from Oracle?
> I am running the following query:
> SELECT SEQ_NUM
> FROM IBSBINO_Physical.IBSBINO
> LIMIT 5
> I expect to get back 5 rows of data, but get back the entire table
> instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira