Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <23355914.37961282938113103.JavaMail.jira@thor>
Date: Fri, 27 Aug 2010 15:41:53 -0400 (EDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Issue Comment Edited: (DERBY-159) When Derby runs in Network
 Server mode, client does not receive warnings generated by Derby - should
 get documented
In-Reply-To: <426955246.1109960986942.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903561#action_12903561 ] 

Dag H. Wanvik edited comment on DERBY-159 at 8/27/10 3:40 PM:
--------------------------------------------------------------

DERBY-4471 adds a variant of JDBC.assertResultSetMethod which asserts on result set warnings. Currently, this functionaility is disabled when running the tests with the client driver due to this issue (I think - not verified).  It would be good to update assertResultSetMethod when this issue is fixed.

      was (Author: dagw):
    DERBY-4471 adds a variant of JDBC.assertResultSetMethod which asserts on result set warnings. Currently, this functionaility is disabled when running the tests with the client driver due to this issue.  It would be good to update assertResultSetMethod when this issue is fixed.
  
> 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
>         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.