[DERBY-1151] ij does not issue a warning if the attribute verifyKey.dat is set on an embedded URL.

• Type: Bug
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 10.1.2.1
• Component/s: Tools
• Labels: derby_triage10_8
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 25/Mar/06 07:42
• Updated: 28/Dec/12 10:31

Description

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.

Issue Links

• is related to: DERBY-2696 ij reports "Attribute is unknown to Derby" on collate, ssl and some other new attributes.
• relates to: DERBY-5970 Check that connection attributes have legal values.
• relates to: DERBY-2697 Implement ij.URLCheck property semantics for client driver