db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4886) Client and embedded don't agree on connection attributes in DatabaseMetaData.getURL()
Date Wed, 16 Feb 2011 14:41:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-4886:
---------------------------------

    Urgency: Low

> Client and embedded don't agree on connection attributes in DatabaseMetaData.getURL()
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-4886
>                 URL: https://issues.apache.org/jira/browse/DERBY-4886
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.7.1.1
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_8
>         Attachments: GetURL.java
>
>
> 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

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message