You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Srinivasa (JIRA)" <ji...@apache.org> on 2007/09/21 07:18:50 UTC
[jira] Created: (OPENJPA-379) StoreException when using a third
party connection pool against Sybase
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: 1.0.0, 0.9.7, 0.9.6, 0.9.0
Environment: Sybase
JConnect drivers
Reporter: Srinivasa
Priority: Minor
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.
[jira] Resolved: (OPENJPA-379) StoreException when using a third
party connection pool against Sybase
Posted by "Srinivasa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srinivasa resolved OPENJPA-379.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
> 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.
[jira] Updated: (OPENJPA-379) StoreException when using a third
party connection pool against Sybase
Posted by "Srinivasa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srinivasa updated OPENJPA-379:
------------------------------
When the statement is created if the resultSetType is not specified - setFetchSize or setCursorName calls result in the ResultSet with TYPE_FORWARD_ONLY and CONCUR_UPDATABLE.
http://manuals.sybase.com/onlinebooks/group-jc/jcg0600e/prjdbc/@Generic__BookTextView/3956
> 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
>
> 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.
[jira] Commented: (OPENJPA-379) StoreException when using a third
party connection pool against Sybase
Posted by "Srinivasa (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (OPENJPA-379) StoreException when using a third
party connection pool against Sybase
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ 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.