[
https://issues.apache.org/jira/browse/DERBY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase closed DERBY-159.
---------------------------
Bug behavior facts: (was: Embedded/Client difference)
Fixed as a result of DERBY-5191 fixes. Changes appeared in 10.8.2
documentation, so closing.
> When Derby runs in Network Server mode, client does not receive warnings
> generated by Derby - should get documented
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-159
> URL: https://issues.apache.org/jira/browse/DERBY-159
> Project: Derby
> Issue Type: Bug
> Components: Documentation, Network Server
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1
> Reporter: Mamta A. Satoor
> Assignee: Kim Haase
> Labels: derby_triage10_5_2
> Fix For: 10.8.2.2, 10.9.0.0
>
> Attachments: d159.java
>
>
> A simple code below will demonstrate that warnings generated by Derby running
> in Server mode do not make their way to client. The client code below is
> trying to create the database db1drda which already exsits. Server generates
> a warning for that but the client cde below does not print it.
> con =
> DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true;",
> "app", "app");
> SQLWarning warnings1 = con.getWarnings();
> System.out.println("database exists, should get warning");
> while (warnings1 != null)
> {
> System.out.println("warnings on connection = " + warnings1);
> warnings1 = warnings1.getNextWarning();
> }
--
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
