Great. Just finished adding Derby-931("Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly) for documentation and it is a subset of Derby-911(" Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client. "). In addition, linked Derby-931 to Derby-310("Document and/or change Derby client code to match behavior with Embedded driver where possible.").

On 2/7/06, Satheesh Bandaram <[EMAIL PROTECTED]> wrote:
Right... I think this specific issue could use a sub-task.

Satheesh

Jean T. Anderson wrote:

> A separate doc sub-task would be easier to reliably track. As it is,
> DERBY-310 has lots of linked tasks, which would make it easy for doc
> updates to fall through the cracks, especially since a section in
> DERBY-310 lists several doc sub-tasks.
>
> A doc subtask to DERBY-911 would definitely keep it on the doc radar.
>
>  -jean
>
>
>


Reply via email to