You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Abe White (JIRA)" <ji...@apache.org> on 2007/01/02 22:41:27 UTC
[jira] Commented: (OPENJPA-94) Allow MappingTool and
persistence.xml to support drop-create for database schema
[ http://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461839 ]
Abe White commented on OPENJPA-94:
----------------------------------
Note that the "SynchronizeMappings" property allows you to use all the arguments of the mappingtool. So you can try something like:
buildSchema(SchemaAction=refresh, DropTables=true)
Theoretically, that will drop unused columns and tables while adding any new columns and tables needed for your mappings.
> 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