[
https://issues.apache.org/jira/browse/TORQUE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-84.
------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 4.0)
The solution in the patch is to revert the order by in an inner query so the
limit is once applied from the top side and the next time from the bottom side.
The problems in this approach are:
- There seems to be a problem if sql functions are used in the order by clause.
- one needs to define an ordering in sql even if none is defined in the query.
- aliases in the order by clause are complicated
The decision is not to replace the current (working) solution (only limit
handled natively) by a solution which might be a bit faster but does not always
work / does unexpected things, but instead implement an extra dapter for mssql
2012 which has native limt and offset support.
> Limit/Offset solution for MSSQL Server
> --------------------------------------
>
> Key: TORQUE-84
> URL: https://issues.apache.org/jira/browse/TORQUE-84
> Project: Torque
> Issue Type: Improvement
> Components: Runtime
> Affects Versions: 3.3
> Environment: MSSQL Server
> Reporter: Tobias Hilka
> Attachments: DBMSSQL.java, DBOracle.java
>
>
> Solved the limit/offset problem for MSSQL. Maybe needs some fine tuning
> according to torque rules.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
