[
https://issues.apache.org/jira/browse/DERBY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730945#action_12730945
]
Myrna van Lunteren commented on DERBY-159:
------------------------------------------
[10.5.2 Triage]
This issue may have gotten into a confusing state because of David's
concerns...
Whether the community should find another network connection model than
NetworkServer/DerbyClient and/or another protocol than DRDA is a different
issue from what we see here - unintuitive current behavior.
I think making this a documentation issue makes sense. But where should this
get documented?
This is a network server/client limitation (currently - because of drda
limitation), but create=true, which is really where it's limited, is not
documented per se there, it's a shared connection Attribute documented on
ref/rrefattrib26867.dita.
And it's an odd location to go into details on this specific case there.
Perhaps somehow on adminguide\cadminappsclient.html
(src/adminguide/cadminappsclient.dita)? Perhaps under the retrieveMessageText
entry?
Or is there somewhere better?
> When Derby runs in Network Server mode, client does not receive warnings
> generated by Derby
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-159
> URL: https://issues.apache.org/jira/browse/DERBY-159
> Project: Derby
> Issue Type: Bug
> Components: 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
>
> 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.