db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-159) When Derby runs in Network Server mode, client does not receive warnings generated by Derby - should get documented
Date Tue, 14 Jul 2009 21:21:14 GMT

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

Myrna van Lunteren commented on DERBY-159:
------------------------------------------

re retrieveMessageText / retrieveMessagesFromServerOnGetMessage: this is a really old bug,
and reflects IBMs db2jcc client, of which there should be no mention in our documentation.
Didn't we/you recently scrub the last remnants out?
Maybe the references should get scrubbed from the sample programs too...But that's another
issue.

The derbyclient equivalent of the long property in the bug report (which value was false by
default) is retrieveMessageText. In addition to being much shorter and to the point, its value
is 'true' by default.

I believe the problem is that warnings generated from the passing of the url during the connection
attempt cannot be returned to the client. If there is an error, the connection just fails
and that will give a client error, I think. Once the connection has been made with retrieveMessageText=true
(which is the default) both warnings and errors should get returned.






> 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.


Mime
View raw message