db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Levitt <de...@mylevita.com>
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
Date Tue, 07 Mar 2006 21:11:29 GMT
Hi Mamta, thanks for the info.  One last question: 
What do you mean by "no-op?"



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

>     [
>
http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12369158
> ] 
> 
> 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
> 
> 


Mime
View raw message