You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Catalina Wei (JIRA)" <ji...@apache.org> on 2007/10/02 01:22:50 UTC

[jira] Resolved: (OPENJPA-389) em.getTransaction().commit() is not issuing database commit for NativeQuery requesting updates

     [ https://issues.apache.org/jira/browse/OPENJPA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Catalina Wei resolved OPENJPA-389.
----------------------------------

    Resolution: Fixed

fix committed under  revision 581088 (trunk) and 581083 (branch 1.0.x)

> em.getTransaction().commit() is not issuing database commit for NativeQuery requesting updates
> ----------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-389
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-389
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.0, 1.0.1, 1.1.0
>            Reporter: Catalina Wei
>            Assignee: Catalina Wei
>             Fix For: 1.0.1, 1.1.0
>
>
> If update is requested by a native query and it is the only method run in the application, 
> following query.executeUpdate(), 
> em.getTransaction().commit(0 is not issuing database commit.
> If after that, em.close() was not issued, any subsequent query againt the same table which involved in the previous 
> native query update will get blocked.

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