[
https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-5516.
------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
Issue & fix info: (was: Patch Available)
Thanks again for the preternaturally fast response, Rick!
Committed patch DERBY-5516.diff to documentation trunk at revision 1329979.
> Document the fact that attributes on the connection URL trump attributes
> specified in a connection Properties object.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5516
> URL: https://issues.apache.org/jira/browse/DERBY-5516
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JDBC
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Fix For: 10.9.0.0
>
> Attachments: DERBY-5516.diff, DERBY-5516.stat, DERBY-5516.zip
>
>
> Attributes for a Derby connection can be set via semicolon-separated lists on
> the connection url as well as in a Properties object passed to the
> java.sql.DriverManager.getConnection() and java.sql.Driver.connect() methods.
> The JDBC spec does not indicate what should happen if an attribute is
> specified both on the connection url and in the Properties object. For some
> databases, like Derby, the attributes on the connection url trump the
> attributes in the Properties object. For other databases, like MySQL, the
> reverse is true.
> Because the JDBC spec does not dictate standard behavior here, we should
> document what Derby does. This information would be useful in some or all of
> the following sections:
> Reference Manual:
> Setting attributes for the database connection URL
> Attributes of the Derby database connection URL
> java.sql.Driver interface
> java.sql.DriverManager.getConnection method
> Developer's Guide:
> Working with the database connection URL attributes
> Specifying attributes in a properties object
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
