[ 
http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12428325 ] 
            
Mamta A. Satoor commented on DERBY-931:
---------------------------------------

Laura, here are answers to your questions.
1)It is a method.
2)It should be referred as Connection.setReadOnly
3 and 4)This method takes a boolean parameter. When true is passed as the 
parameter, the user is asking that the driver make this Connection as 
read-only. In embedded mode, this method with true value will correctly mark 
the Connection as read-only and this can be verified by calling 
Connection.isReadOnly method which will return true. With Netwrok Client 
Driver, the Connection.setReadOnly(true) does not make the Connection object as 
read-only and this can be checked by calling Connection.isReadOnly() which will 
return false. 
The documentation at http://db.apache.org/derby/docs/10.1/ref/rrefjavcsro.html 
implies that Derby supports Connection.setReadOnly for both embedded and 
Network Server mode. But since that is not true, we should document it as a 
difference between the 2 drivers.

Just a suggestion for little change to Title text
Title - Differences using the Connection.setReadOnly method 


> 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

        

Reply via email to