karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Corsi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-1572) Add SQL Server Support for JDBC Lock
Date Tue, 10 Jul 2012 19:16:34 GMT

    [ https://issues.apache.org/jira/browse/KARAF-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410724#comment-13410724

Claudio Corsi commented on KARAF-1572:

The updates that you are requesting are reasonable.  Do you want me to make these changes
or do you want to do them?

I understand that you do not want to add new features to the 2.2.x branch but there is a customer
of ours that would like to be able to use SQL Server as a jdbc lock but they are using karaf

It would be great if we could include this feature with that branch and/or update the current
jdbc lock implementation to be able to use SQL Server.

> 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
>             Fix For: 2.2.9, 2.3.1, 3.1.0
>         Attachments: 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


View raw message