db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5907) Warnings missing on client driver
Date Mon, 24 Sep 2012 20:12:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-5907:

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
> 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
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_10
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message