[DERBY-4886] Client and embedded don't agree on connection attributes in DatabaseMetaData.getURL()

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.7.1.1
• Component/s: JDBC
• Labels: derby_triage10_8
• Urgency: Low
• Issue & fix info: Repro attached
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 05/Nov/10 10:11
• Updated: 16/Feb/11 14:39

Description

The embedded driver strips away all connection attributes before returning the URL from DatabaseMetaData.getURL(). The client driver also returns the connection attributes (except user and password, see DERBY-559).

The attached repro (GetURL.java) demonstrates this behaviour (note that it uses both connection attributes directly in the URL and connection attributes in a java.util.Properties object):

Connecting with URL jdbc:derby:wombat;create=true and properties

{territory=no_NO}
getURL() => jdbc:derby:wombat

Connecting with URL jdbc:derby://localhost/wombat;create=true and properties {territory=no_NO}

getURL() => jdbc:derby://localhost:1527/wombat;create=true;territory=no_NO