[
http://jira.codehaus.org/browse/MOPENJPA-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved MOPENJPA-30.
-----------------------------------
Resolution: Fixed
> add option to directly write to the database
> --------------------------------------------
>
> Key: MOPENJPA-30
> URL: http://jira.codehaus.org/browse/MOPENJPA-30
> Project: Maven 2.x OpenJPA Plugin
> Issue Type: New Feature
> Affects Versions: 1.1
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2
>
>
> Reported by Patrick Linskey:
> I'm trying to use openjpa-maven-plugin in my test framework to push =
> changes to the database. However, I've run into a problem:=20
> The sqlFile parameter has a default value, so it cannot be left unset. =
> Since OpenJPA's MappingTool interprets a set value to mean "don't touch =
> the database -- just write to this file instead", OpenJPA can never hit =
> the database instead. The JavaDocs make it sound as though this might be =
> an unintended consequence (maybe the default was added at some point?), =
> so I introduced a new parameter called 'modifyDatabase' which bypasses =
> the sqlFile parameter if set.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
