openjpa-dev mailing list archives

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

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

Srinivasa commented on OPENJPA-379:
-----------------------------------

Yes my initial thought too was to override the prepareStatement(...) behavior in SybaseDictionary$SybaseConnection.
But later noticed that our connection pool implementation is setting the ResultSetType for
all DBs, so to keep it consistent I went the route of setting it at the DelegatingConnection
level. 

> 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