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 "Laura Stewart (JIRA)" <de...@db.apache.org> on 2006/08/16 01:39:15 UTC

[jira] Commented: (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=comments#action_12428265 ] 
            
Laura Stewart commented on DERBY-931:
-------------------------------------

I propose the following text, but I have a few questions below..

Title - Differences using the setReadOnly method 
Text - The setReadOnly method performs as expected in the embedded mode, however in the client-server mode the setReadOnly method ignores options

Questions:
1. Is this a method, property, attribute, or ???
2. Should this method be referred to as Connect.setReadOnly?
3. The "options", are these options that the user sets when they specify this method?
4. We might want to consider changing "as expected" to something more specific.   I looked up Connect.setReadOnly and all our documentation says is that it is supported. What does this method actually do?

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