Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <9196855.1155746535571.JavaMail.jira@brutus>
Date: Wed, 16 Aug 2006 09:42:15 -0700 (PDT)
From: "Laura Stewart (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@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
In-Reply-To: <582466368.1139340177272.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12428430 ] 
            
Laura Stewart commented on DERBY-931:
-------------------------------------

Mamta, I changed the title and the text. 
Is this now accurate?

In the embedded mode, when the Connection.setReadOnly method has "true" as
the parameter, the connection is marked as a read-only connection. When using
a Network Server, the Connection.setReadOnly(true) method is ignored and the
connection is not marked as a read-only connection.

> 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