Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6706

Derby does not check invalid configuration option name in derby.properties

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.10.2.0
    • Fix Version/s: None
    • Component/s: Miscellaneous
    • Environment:
      all
    • Urgency:
      Normal

      Description

      Dear Derby Developers,

      This is a simple-to-fix but annoying problem in Derby.

      Derby simply does not check an invalid configuration option name specified in derby.properties.

      For example,

      if I want to set:

      derby.database.forceDatabaseLock=False

      However, I mis-spell the configuration name, like:

      ddddddddddddderby.database.forceDatabaseLock=False

      Seems that derby simply ignores this mis-spelled configuration option rather than issuing a warning to inform me the potential problems in using Derby. This happens to me a few times, and is really annoying.

      I would suggest to check the validity of every configuration option name in the configuration file. Please let me know your thoughts.

      -Sai

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                szhang Sai Zhang
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified