[
http://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461857
]
Patrick Linskey commented on OPENJPA-94:
----------------------------------------
One downside of dropping and re-creating schemas is the latency of the
operation. I think that it'd be more useful to have an option to automatically
delete all records from all mapped tables. This option could potentially also
work lazily if a full class list is not available up-front -- OpenJPA could
issue a delete statement when a new ClassMapping is first initialized.
> Allow MappingTool and persistence.xml to support drop-create for database
> schema
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-94
> URL: http://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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
