ij does not issue a warning if the attribute verifyKey.dat is set on an
embedded URL.
-------------------------------------------------------------------------------------
Key: DERBY-1151
URL: http://issues.apache.org/jira/browse/DERBY-1151
Project: Derby
Type: Bug
Components: Tools
Reporter: Daniel John Debrunner
Priority: Trivial
ij has code to check that the JDBC attributes on a URL are valid for embedded.
It obtains the list of attributes by using reflection on the Attributes class
for the list fo fields.
The field Attribute.CRYPTO_EXTERNAL_KEY_VERIFY_FILE is not an attribute and so
this constant should be elsewhere,, most likely with the encryption code.
Also going through the list of fields may not be the best approach for getting
the list of valid attributes. A simple array of valid attributes
may be a much clearer and easier solution. Especially if the Attribute class
contains client side attributes as well, as a future version might.
ij> connect 'jdbc:derby:fred;foo=true';
URL Attribute [foo=true]
Attribute is unknown to Derby.
ERROR XJ004: Database 'fred' not found.
ij> connect 'jdbc:derby:fred;verifyKey.dat=fr
ERROR XJ004: Database 'fred' not found.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
