openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-379) StoreException when using a third party connection pool against Sybase
Date Fri, 21 Sep 2007 15:07:51 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529455
] 

Michael Dick commented on OPENJPA-379:
--------------------------------------

I'm not sure this was the right fix for the problem. The change affects all databases not
just Sybase. 

It seems to me that the correct fix would be to delegate the resultSet type to the DBDictionary
class, rather than changing the settings for all databases. 



> StoreException when using a third party connection pool against Sybase 
> -----------------------------------------------------------------------
>
>                 Key: OPENJPA-379
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-379
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0
>         Environment: Sybase
> JConnect drivers
>            Reporter: Srinivasa
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> org.apache.openjpa.util.DataStoreException: Cursor 'jconnect_implicit_1' was declared
with a FOR UPDATE clause. This cursor was found to be read only.
> When running queries using third party connection pool and JConnect  drivers

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message