db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5907) Warnings missing on client driver
Date Thu, 11 Sep 2014 19:10:35 GMT

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

Kim Haase commented on DERBY-5907:

Note that the documentation referred to here involves error messages, not the user documentation.

> Warnings missing on client driver
> ---------------------------------
>                 Key: DERBY-5907
>                 URL: https://issues.apache.org/jira/browse/DERBY-5907
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, Network Client, Network Server
>    Affects Versions:
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_10, derby_triage10_11
> Now that we have more or less agreed we can superset DRDA, I think we should revisit
the missing warnings, e.g. DERBY-159: connecting against an existing database gives no warning
on the client.
> Once we can handle warnings on a par with embedded, we can probably we should also generate
warnings for wrong connection attributes on the server side, and remove such logic from ij.

This message was sent by Atlassian JIRA

View raw message