[
https://issues.apache.org/jira/browse/TORQUE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483915
]
Thomas Fischer commented on TORQUE-84:
--------------------------------------
- Regarding the oracle part: Could you describe what your change to the
limit/offset functionality does ? An example (failing with the old
implementation, and working with your implementation) would be great.
- Regarding the useEscapeClauseForLike() part: I assume this is to circumvent
the problems described in TORQUE-70. But with your solution, using backslashes
in like clauses will not work at all. I'd think a better solution would be to
leave the useEscapeClauseForLike() function in DBOracle as it is, but append
the 'ESCAPE \' part only if a backslash appears in the query. So this would
have the effect that escapes would be working in VARCHAR columns, and
non-escaped LIKE queries would be working for NVARCHAR columns. Only escaped
LIKE queries for NVARCHAR columns would not be working, but this is already the
case now. What do you think ?
> 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]
