[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461899
]
Patrick Linskey commented on OPENJPA-94:
----------------------------------------
I added an optimization for MySQL with r492032, but disabled it by default
since http://dev.mysql.com/doc/refman/5.0/en/delete.html mentions that it may
fail if using InnoDB and delete constraints.
> Allow MappingTool and persistence.xml to support drop-create for database
> schema
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-94
> URL: https://issues.apache.org/jira/browse/OPENJPA-94
> Project: OpenJPA
> Issue Type: New Feature
> Reporter: Shay Banon
>
> Currently, in the persistence context, one can define:
> <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema" />
> Which causes OpenJPA to build the database schema based on the mapping
> defined. Currently, there is no way to define it to drop tables if they
> exists before creating the database schema. This is very useful for tests
> that drop (if exists) and creates new tables for each test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
