Uploaded image for project: 'Isis'
  1. Isis
  2. ISIS-1171

If DN autoCreate is missing, don't default to "true", instead default to "false".

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • core-1.8.0
    • 1.9.0
    • Isis Persistence JDO
    • None

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

      Attachments

        Activity

          People

            Unassigned Unassigned
            danhaywood Daniel Keir Haywood
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: