You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/07/09 19:35:04 UTC
[jira] [Created] (ISIS-1171) If DN autoCreate is missing, don't
default to "true", instead default to "false".
Dan Haywood created ISIS-1171:
---------------------------------
Summary: If DN autoCreate is missing, don't default to "true", instead default to "false".
Key: ISIS-1171
URL: https://issues.apache.org/jira/browse/ISIS-1171
Project: Isis
Issue Type: Improvement
Components: Core
Affects Versions: core-1.8.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
With the current 1.8.0 behaviour, if an application did not specify the "datanucleus.autoCreateSchema" property (eg due to a typo), then the framework would default this property to "true". This could result in the target database being modified.
So, instead, we should default this to "false", to avoid such accidents. Note that in 1.9.0 the name of this property changes to "datanucleus.schema.autoCreateAll", but the intent is the same.
~~~
Also, note that there is similar functionality for validation; "datanucleus.autoValidateAll" is defaulted to true if missing. This behaviour does _not_ need to change as their are no ill side-effects. NB: in 1.9.0 note that the name of this property changes to "datanucleus.schema.autoValidateAll".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)