Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.10.2.0
-
None
-
all
-
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
- relates to
-
DERBY-5970 Check that connection attributes have legal values.
- Open
-
DERBY-2844 PropertyUtil should not silently ignore syntax errors in a property file
- Open