[
https://issues.apache.org/jira/browse/KARAF-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436542#comment-13436542
]
Andreas Pieber edited comment on KARAF-1572 at 8/17/12 2:45 PM:
----------------------------------------------------------------
should we really apply this to 2.2.10? Independently of semver.org I think we
should stop introducing new features (and therefore new potential bugs) into
the quite old 2.2.x branch. Just 0.02€ from my gut feeling :-)
was (Author: pieber):
should we really apply this to 2.2.10? Independently of semver.org I think
we should stop introducing new features (and therefore new potential bugs)
hinto the quite old 2.2.x branch. Just 0.02€ from my gut feeling :-)
> Add SQL Server Support for JDBC Lock
> -------------------------------------
>
> Key: KARAF-1572
> URL: https://issues.apache.org/jira/browse/KARAF-1572
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-instance
> Affects Versions: 2.2.7
> Reporter: Claudio Corsi
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.10, 2.3.1, 3.1.0
>
> Attachments: GenericJDBCLock.patch, GenericJDBCLock.patch
>
>
> The current JDBCLock implementations do not work when using Microsoft SQL
> Server since this requires that you use a CURSOR with the SELECT statement.
--
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
