it's good with sensitive too Slavic
Dag H. Wanvik wrote: > Hi Veaceslav, > > >>>>>>"Veaceslav" == Veaceslav Chicu <[EMAIL PROTECTED]> wrote: > > Veaceslav> > Veaceslav> it's about simple tables, with text, numeric fields > Veaceslav> I want to scoll and change rows, > Veaceslav> > Veaceslav> > Veaceslav> rezults conform to isolation levels > > In the example you provided in the bug you filed > (http://issues.apache.org/jira/browse/DERBY-605), you used > TYPE_SCROLL_INSENSITIVE. This would give extra isolation (think > snapshot), in addition to that provided by SQL's isolation > levels. Actually, SQL prohibits insensitive scrollable cursors in > combination with update, although JDBC allows it, because some vendors > support it. Sensitive result sets makes changes made by other > transactions visible in the result set. If you just want the isolation > provided by SQL, you would want to use TYPE_SCROLL_SENSITIVE. > > For Derby, we will probably want to build sensitive (first), to be SQL > compliant. > > Dag > > Veaceslav> > Veaceslav> best regards, > Veaceslav> Slavic > Veaceslav> > Veaceslav> > Veaceslav> Satheesh Bandaram wrote: > Veaceslav> > Looks like we are talking about two different issues. I meant to > reply > Veaceslav> > to another thread that asked about scrollable cursors and large > objects: > Veaceslav> > > Veaceslav> > > http://mail-archives.apache.org/mod_mbox/db-derby-user/200510.mbox/[EMAIL > PROTECTED] > Veaceslav> > > Veaceslav> > Satheesh > Veaceslav> > > Veaceslav> > Veaceslav Chicu wrote: > Veaceslav> > > Veaceslav> >>DERBY-605 > Veaceslav> >> > Veaceslav> >>maybe someone can reformulate this > Veaceslav> >> > Veaceslav> >>I tried in embeded mode it doesn't scroll and update > Veaceslav> >>I have not much free time now, I can help testing > Veaceslav> >> > Veaceslav> >>Slavic > Veaceslav> >> > Veaceslav> >>Satheesh Bandaram wrote: > Veaceslav> >> > Veaceslav> >> > Veaceslav> >>>I am also willing to help anyone interested in enhancing Derby > to > Veaceslav> >>>support this. > Veaceslav> >>> > Veaceslav> >>>Kathey Marsden wrote: > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>>>Currently, we do not have large object locators (DERBY-208) > and I think > Veaceslav> >>>>that is a prerequisite for this feature. > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>While adding large object locators would be a great thing for > Derby, > Veaceslav> >>>wondering if there is any way to implement this without > locators. Since > Veaceslav> >>>embedded driver is able to support scrollable cursors with large > Veaceslav> >>>objects, would it be possible to expose this through network > Veaceslav> >>>server/client, even if large objects need to be materialized on > the > Veaceslav> >>>client? I am willing to help enhance Derby Client side, which > may be the > Veaceslav> >>>easy part. :-) > Veaceslav> >>> > Veaceslav> >>>Large object locators have many other usages too, so these are > good to > Veaceslav> >>>consider at sometime. > Veaceslav> >>> > Veaceslav> >>>Satheesh > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>>>Large objects are > Veaceslav> >>>>materialized on the client which is a big issue and not just > for for > Veaceslav> >>>>scrollable cursors. > Veaceslav> >>>> > Veaceslav> >>>>Kathey > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >>> > Veaceslav> >> > Veaceslav> >> > Veaceslav> >> > Veaceslav> >> > Veaceslav> >> > Veaceslav>
