You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/07/20 22:04:06 UTC

[jira] Updated: (OPENJPA-89) Bulk delete fails to delete owned many-to-many relationship (entry remains in join table)

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

Patrick Linskey updated OPENJPA-89:
-----------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: OPENJPA-290

> Bulk delete fails to delete owned many-to-many relationship (entry remains in join table)
> -----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-89
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-89
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel
>         Environment: Using Apache Derby (10.2.1.6)
>            Reporter: David Ezzio
>            Assignee: Marc Prud'hommeaux
>             Fix For: 0.9.8
>
>         Attachments: BugOJPA-89.zip
>
>
> When executing the statement 
> em.createQuery("delete from Subject").executeUpdate();
> where Subject is in a many-to-many relationship with Book, and Subject owns the relationship, one expects that the corresponding entry in the SUBJECT_BOOK table would be deleted.  This happens when bulk deleting one-to-many relationships that are mapped with a join table, as well as for *-to-one relationships mapped with a foreign key.  It also happens when individually deleting objects.  However, it does not happen when bulk deleting the owning side of a many-to-many relationship.

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