You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Martin Dirichs (JIRA)" <ji...@apache.org> on 2009/05/07 12:30:30 UTC
[jira] Created: (OPENJPA-1070) Restore support for composite
foreign keys on MySQL
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
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.
[jira] Assigned: (OPENJPA-1070) Restore support for composite
foreign keys on MySQL
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar reassigned OPENJPA-1070:
--------------------------------------
Assignee: Pinaki Poddar
> 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.
[jira] Updated: (OPENJPA-1070) Restore support for composite
foreign keys on MySQL
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1070:
----------------------------------
Fix Version/s: 2.0.0-M2
> 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-M2
> Reporter: Martin Dirichs
> Assignee: Pinaki Poddar
> Priority: Minor
> Fix For: 2.0.0-M2
>
>
> 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.
[jira] Resolved: (OPENJPA-1070) Restore support for composite
foreign keys on MySQL
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ 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.