You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (Created) (JIRA)" <ji...@apache.org> on 2011/12/01 21:54:40 UTC
[jira] [Created] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
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
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
[jira] [Assigned] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
Posted by "Kim Haase (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-5516:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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
[jira] [Updated] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5516:
-----------------------------
Attachment: DERBY-5516.zip
DERBY-5516.stat
DERBY-5516.diff
Thanks for the guidance, Rick. I'm attaching DERBY-5516.diff, DERBY-5516.stat, and DERBY-5516.zip, with changes to the following:
M src/devguide/cdevdvlp51654.dita
M src/devguide/tdevdvlp36289.dita
M src/ref/rrefattrib24612.dita
M src/ref/rrefjdbc34565.dita
M src/ref/rrefjdbc10889.dita
The java.sql.Driver topic didn't seem like a logical place to put this information. I looked for other possibilities, but I think you found the best locations.
Please let me know what changes might be needed here.
> 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
> 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
[jira] [Closed] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-5516.
----------------------------
Changes have appeared in Latest Alpha Manuals.
> 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
[jira] [Commented] (DERBY-5516) Document the fact that attributes
on the connection URL trump attributes specified in a connection Properties
object.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260847#comment-13260847 ]
Rick Hillegas commented on DERBY-5516:
--------------------------------------
Thanks, Kim. These changes look good to me. +1
> 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
> 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
[jira] [Resolved] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5516) Document the fact that attributes on
the connection URL trump attributes specified in a connection Properties
object.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5516:
-----------------------------
Issue & fix info: Patch Available
> 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
> 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