[
https://issues.apache.org/jira/browse/DERBY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-159:
-------------------------------------
Attachment: d159.java
attaching an updated repro - this repro uses derbyclient and correct/current
url.
The repro expects network server to have been started before it's run.
Note that retrieveMessageText is true by default, so is not really needed in
the url for derbyclient.
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
