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)" <ji...@apache.org> on 2013/06/13 23:09:20 UTC

[jira] [Updated] (DERBY-5907) Warnings missing on client driver

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

Kathey Marsden updated DERBY-5907:
----------------------------------

    Affects Version/s: 10.10.1.1
               Labels: derby_triage10_10 derby_triage10_11  (was: derby_triage10_10)
    
> 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: 10.10.1.1
>            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 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