db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-931) Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
Date Wed, 16 Aug 2006 17:10:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12428441 ] 
            
Mamta A. Satoor commented on DERBY-931:
---------------------------------------

Laura, that looks good.

> 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

        

Mime
View raw message