You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org> on 2004/11/07 09:09:32 UTC

[jira] Closed: (GERONIMO-429) Foreign key constraints are not enforced for CMP 2.x EntityBean

     [ http://nagoya.apache.org/jira/browse/GERONIMO-429?page=history ]
     
Gianny DAMOUR closed GERONIMO-429:
----------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M3

This capability has been implemented. The optional element enforce-foreign-key-constraints indicates if DML operations associated to CMP EJB need to be sorted to enforce foreign key constraints.


> Foreign key constraints are not enforced for CMP 2.x EntityBean
> ---------------------------------------------------------------
>
>          Key: GERONIMO-429
>          URL: http://nagoya.apache.org/jira/browse/GERONIMO-429
>      Project: Apache Geronimo
>         Type: New Feature
>   Components: OpenEJB
>     Versions: 1.0-M2
>     Reporter: Gianny DAMOUR
>     Assignee: Gianny DAMOUR
>      Fix For: 1.0-M3

>
> The EJB specifications do not require CMP 2.x containers to enforce foreign key constraints. Such a capability seems to be a quality of implementation, that OpenEJB will support.
> An element needs to be added to the OpenEJB DD in order to turn on such a capability. When activated, the flush strategy used under the cover of the transactional cache re-arranges the SQL operations to avoid foreign key constraint conflicts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira