[
https://issues.apache.org/jira/browse/TORQUE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494032
]
Tobias Hilka commented on TORQUE-84:
------------------------------------
Limit/Offset patch: The implementation used so far in Torque does not consider
function calls in SQL statements. In the implementation Torque makes use of
nested Select statements which does not work poperly when using functions like
UPPER(name). There is an extra comment in the code stating that functions are
not supported so far. Now, this limit/offset also works for functions like
UPPER(..). I am sorry, but I don't have a sample SQL statement at hand. As far
as I remember the problem occured when joining tables which have some equally
named columns but no aliases.
Unicode problems appeared at the following places:
SQLExpression.buildLike(...): Escape clause can not be switched between unicode
and none-unicode support.
SQLExpression.build(...), .buildLike(...), .processInValue(...)
> 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
> Fix For: 3.3
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
