db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta Satoor" <msat...@gmail.com>
Subject Re: [jira] Created: (DERBY-931) Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
Date Mon, 27 Feb 2006 18:39:38 GMT
Jira seems to be down. I wanted to change the fix versoin to 10.2. I have a
customer who ran into this problem and they would like to see this
documented in 10.2 release. Jeff, thanks for working on it.

thanks,
Mamta


On 2/7/06, Mamta A. Satoor (JIRA) <derby-dev@db.apache.org> wrote:
>
> 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