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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2005/08/20 01:49:54 UTC

[jira] Commented: (DERBY-159) When Derby runs in Network Server mode, client does not receive warnings generated by Derby

    [ http://issues.apache.org/jira/browse/DERBY-159?page=comments#action_12319441 ] 

Kathey Marsden commented on DERBY-159:
--------------------------------------

I think this type of warning cannot be sent within the protocol specification.  I think it will have to be changed to a documentation issue.

> When Derby runs in Network Server mode, client does not receive warnings generated by Derby
> -------------------------------------------------------------------------------------------
>
>          Key: DERBY-159
>          URL: http://issues.apache.org/jira/browse/DERBY-159
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira