[CAUSEWAY-1171] If DN autoCreate is missing, don't default to "true", instead default to "false".

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: core-1.8.0
• Fix Version/s: 1.9.0
• Component/s: Persistence JDO
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 09/Jul/15 17:34
• Updated: 01/Sep/15 19:49
• Resolved: 28/Jul/15 20:09

Description

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".