[
https://issues.apache.org/jira/browse/OPENJPA-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717216#action_12717216
]
Milosz Tylenda commented on OPENJPA-1083:
-----------------------------------------
I have checked the latest docs of DB2, Derby, Firebird, MySQL, Oracle,
PostgreSQL, SQL Server and Sybase 11and it seems that only MySQL does not like
DROP CONSTRAINT and needs DROP FOREIGN KEY key_name.
Maybe this issue could be closed and a new one created for updating MySQL
dictionary.
Since MySQL does not understand DROP CONSTRAINT at all, we might also need to
override getDropPrimaryKeySQL. On the other hand, getDropPrimaryKeySQL seems
not to be used with PK name != null. Is there a way for an application to
specify PK constraint name?
> org.apache.openjpa.persistence.kernel.TestEJBState fails with two exceptions
> ORA-00904 and ORA-02275 against oracleDB.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1083
> URL: https://issues.apache.org/jira/browse/OPENJPA-1083
> Project: OpenJPA
> Issue Type: Sub-task
> Affects Versions: 2.0.0-M2
> Reporter: Ravi P Palacherla
> Assignee: Michael Dick
> Fix For: 1.3.0, 2.0.0
>
> Attachments: OPENJPA-1083.patch, OPENJPA-1083_option1.patch,
> OPENJPA-1083_option2.patch, OPENJPA-1083_trunk.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
