openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-1070) Restore support for composite foreign keys on MySQL
Date Sat, 09 May 2009 17:06:45 GMT

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

Pinaki Poddar resolved OPENJPA-1070.
------------------------------------

    Resolution: Fixed

> Restore support for composite foreign keys on MySQL
> ---------------------------------------------------
>
>                 Key: OPENJPA-1070
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1070
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.2.1, 2.0.0
>            Reporter: Martin Dirichs
>            Assignee: Pinaki Poddar
>            Priority: Minor
>
> When creating the database schema for MySQL databases, OpenJPA refuses to define foreign
key constraints for composite keys. Warning message is: openjpa.jdbc.Schema - The foreign
key "<foreignkey>" was not added to table "[...]" The reason for this is that composite
foreign key support is explicitly disabled in MySQLDictionary.
> However, composite foreign keys seem to work flawlessly in recent MySQL versions (such
as 5.0.51a). Probably this limitation in MySQLDictionary thus is historic and can be removed.
> For the corresponding mailing list discussion, see here:
> http://n2.nabble.com/Composite-foreign-keys-with-MySQL-tc2772257.html

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


Mime
View raw message