Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47041 invoked from network); 8 Mar 2006 05:03:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Mar 2006 05:03:06 -0000 Received: (qmail 92816 invoked by uid 500); 8 Mar 2006 05:03:05 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 92782 invoked by uid 500); 8 Mar 2006 05:03:05 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 92773 invoked by uid 99); 8 Mar 2006 05:03:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2006 21:03:05 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of msatoor@gmail.com designates 64.233.182.202 as permitted sender) Received: from [64.233.182.202] (HELO nproxy.gmail.com) (64.233.182.202) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2006 21:03:04 -0800 Received: by nproxy.gmail.com with SMTP id l24so70882nfc for ; Tue, 07 Mar 2006 21:02:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Y2D0JSIyRtiFNmDb632X5WDt9WxcXPQeoc4R+wSBEUNP2Mz8CqeUQptrxBLhSrT4znOidcCudXazmImNSukRt+QltALk9fuEKd9GF664aSq5UW0l/CrY+E8gnE4QHZ7GuxDENk9k6Enn7CytwVVd5FnjfKk1l3+QF6tXd/iCL1E= Received: by 10.49.66.18 with SMTP id t18mr150157nfk; Tue, 07 Mar 2006 21:02:43 -0800 (PST) Received: by 10.49.22.19 with HTTP; Tue, 7 Mar 2006 21:02:43 -0800 (PST) Message-ID: Date: Tue, 7 Mar 2006 21:02:43 -0800 From: "Mamta Satoor" To: derby-dev@db.apache.org Subject: Re: [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: <20060307211129.30969.qmail@web81607.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14808_22214004.1141794163221" References: <1800203021.1141707159584.JavaMail.jira@ajax> <20060307211129.30969.qmail@web81607.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_14808_22214004.1141794163221 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sorry, Jeff. "no-op" here means that setReadOnly call is ignored in the client server mode. On 3/7/06, Jeff Levitt wrote: > > Hi Mamta, thanks for the info. One last question: > What do you mean by "no-op?" > > > > --- "Mamta A. Satoor (JIRA)" > wrote: > > > [ > > > > http://issues.apache.org/jira/browse/DERBY-931?page=3Dcomments#action_123= 69158 > > ] > > > > Mamta A. Satoor commented on DERBY-931: > > --------------------------------------- > > > > I think it is sufficient to add a bullet saying that > > setReadOnly is a no-op in client-server mode, but > > works fine in embedded mode. > > > > > 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 > > > Type: Sub-task > > > Components: Documentation > > > Versions: 10.0.2.1 > > > Reporter: Mamta A. Satoor > > > > > > > > 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 > > > > > > ------=_Part_14808_22214004.1141794163221 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sorry, Jeff. "no-op" here means that setReadOnly c= all is ignored in the client server mode.

On 3/7/06, J= eff Levitt <derby@mylevita.com= > wrote:
Hi Mamta, thanks for the info.&n= bsp; One last question:
What do you mean by "no-op?"
<= br>

--- "Mamta A. Satoor (JIRA)" <derby-dev@db.apache.org>
wrote:

>  = ;   [
>
http://issues.apache.org/jira/browse/DERBY-931?page=3Dcomments#action_12369= 158
> ]
>
> Mamta A. Satoor commented on DERBY-931:> ---------------------------------------
>
> I think it i= s sufficient to add a bullet saying that
> setReadOnly is a no-op in client-server mode, but
> works fi= ne in embedded mode.
>
> > Until Derby-911 gets fixed, docum= ent the
> difference in behavior between Nework Client Driver
> and Embedded Driver for setReadOnly
> >
>
----------= ---------------------------------------------------------------------------= -------------------------------------------
> >
> > =          Key: DERBY-931
> >          UR= L:
> http:= //issues.apache.org/jira/browse/DERBY-931
> >   = ;   Project: Derby
> >     = ;    Type: Sub-task
> >   Components: Doc= umentation
> >     Versions: 10.0.2.1
> >     Reporter: Mamta A. Satoo= r
>
> >
> > Derby 911 "Connection.setReadOnly = is a no-op in
> Network Client. It works fine with embedded client.&q= uot;
> has more details on this issue but basically, we
> should do= cument the difference in behavior for
> setReadOnly between Network D= river and Embedded
> Driver.
>
> --
> This message = is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of
&= gt; the administrators:
>
>
http://issues.apache.org/jira/secure/A= dministrators.jspa
> -
> For more information on JIRA, see:
> &nbs= p;  http://www= .atlassian.com/software/jira
>
>

=
------=_Part_14808_22214004.1141794163221--