You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sai Zhang (JIRA)" <ji...@apache.org> on 2014/08/15 00:06:20 UTC

[jira] [Created] (DERBY-6706) Derby does not check invalid configuration option name in derby.properties

Sai Zhang created DERBY-6706:
--------------------------------

             Summary: Derby does not check invalid configuration option name in derby.properties
                 Key: DERBY-6706
                 URL: https://issues.apache.org/jira/browse/DERBY-6706
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.10.2.0
         Environment: all
            Reporter: Sai Zhang


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



--
This message was sent by Atlassian JIRA
(v6.2#6252)