[jira] Commented: (OPENJPA-1294) Nested JDBC calls fail for certain database

["Milosz Tylenda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENJPA-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754583#action_12754583 ] 

Milosz Tylenda commented on OPENJPA-1294:
-----------------------------------------

Hi Pinaki. I guess the databases affected are those with DBDictionary.supportsMultipleNontransactionalResultSets = false. The name suggests that the problem should occur only while using auto-commit.


> Nested JDBC calls fail for certain database
> -------------------------------------------
>
>                 Key: OPENJPA-1294
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1294
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc, kernel, query, sql
>    Affects Versions: 2.0.0-M3, 2.0.0-M4, 2.0.0
>         Environment: MySQL
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.0.0-M3, 2.0.0-M4, 2.0.0
>
>
> Some use cases require a new database connection to perform operation because the current connection is busy/open.
> Typical use case is asking for size of the result set (obtained by a SELECT COUNT(*) query) while the original result set is still being open.
> Some databases (e.g. MySQL as per observation) do not allow the new COUNT query on the same connection because the original result set is still open.
> A JDBCStore.getNewConnection() is added -- but use it with caution, remember to close it and use it only when required.

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