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 "Jean T. Anderson (JIRA)" <de...@db.apache.org> on 2006/08/16 21:28:16 UTC

[jira] Resolved: (DERBY-931) Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly

     [ http://issues.apache.org/jira/browse/DERBY-931?page=all ]

Jean T. Anderson resolved DERBY-931.
------------------------------------

    Fix Version/s: 10.3.0.0
       Resolution: Fixed
       Derby Info:   (was: [Patch Available])

Committed patch derby931.diff revision 432000.

> Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-931
>                 URL: http://issues.apache.org/jira/browse/DERBY-931
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.0.2.1
>            Reporter: Mamta A. Satoor
>         Assigned To: Laura Stewart
>             Fix For: 10.3.0.0
>
>         Attachments: derby931.diff, derby931_html.zip
>
>
> DERBY-911 "Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client." has more details on this issue but basically, we should document the difference in behavior for setReadOnly between Network Driver and Embedded Driver. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira