Prev: Signature collision between methods in superclass and interface:suggestions?
Next: Signature collision between methods in superclass andinterface: suggestions?
From: gk on 28 Jun 2010 05:41 please look at the doc for ResultSet http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ResultSet.html#TYPE_SCROLL_SENSITIVE TYPE_SCROLL_SENSITIVE public static final int TYPE_SCROLL_SENSITIVEThe constant indicating the type for a ResultSet object that is scrollable and generally sensitive to changes made by others. What it means by "generally sensitive to changes made by others" ? I don't get this part.
From: RedGrittyBrick on 28 Jun 2010 06:55 On 28/06/2010 10:41, gk wrote: > please look at the doc for ResultSet > > http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ResultSet.html#TYPE_SCROLL_SENSITIVE > > TYPE_SCROLL_SENSITIVE > public static final int TYPE_SCROLL_SENSITIVEThe constant indicating > the type for a ResultSet object that is scrollable and generally > sensitive to changes made by others. > > What it means by "generally sensitive to changes made by others" ? I > don't get this part. For general questions of this sort, you'll often get an adequate answer by searching using Google or some other search engine: http://en.wikipedia.org/wiki/Cursor_%28databases%29 "Scrollable cursors can potentially access the same row in the result set multiple times. Thus, data modifications (insert, update, delete operations) from other transactions could have an impact on the result set. A cursor can be SENSITIVE or INSENSITIVE to such data modifications. A sensitive cursor picks up data modifications impacting the result set of the cursor, and an insensitive cursor does not." Note that this is really an SQL question, more than a Java question. Sometimes you'll get more relevant answers to DBMS-specific SQL questions in an appropriate database newsgroup or forum. -- RGB
From: gk on 28 Jun 2010 07:26 On Jun 28, 3:55 pm, RedGrittyBrick <RedGrittyBr...(a)spamweary.invalid> wrote: > On 28/06/2010 10:41, gk wrote: > > > please look at the doc for ResultSet > > >http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ResultSet.html#TYPE_... > > > TYPE_SCROLL_SENSITIVE > > public static final int TYPE_SCROLL_SENSITIVEThe constant indicating > > the type for a ResultSet object that is scrollable and generally > > sensitive to changes made by others. > > > What it means by "generally sensitive to changes made by others" ? I > > don't get this part. > > For general questions of this sort, you'll often get an adequate answer > by searching using Google or some other search engine: > > http://en.wikipedia.org/wiki/Cursor_%28databases%29 > > "Scrollable cursors can potentially access the same row in the result > set multiple times. Thus, data modifications (insert, update, delete > operations) from other transactions could have an impact on the result > set. A cursor can be SENSITIVE or INSENSITIVE to such data > modifications. A sensitive cursor picks up data modifications impacting > the result set of the cursor, and an insensitive cursor does not." > > Note that this is really an SQL question, more than a Java question. > Sometimes you'll get more relevant answers to DBMS-specific SQL > questions in an appropriate database newsgroup or forum. > > -- > RGB Thanks . your post was very much helpful.
From: gk on 28 Jun 2010 07:52 On Jun 28, 4:26 pm, gk <src...(a)gmail.com> wrote: > On Jun 28, 3:55 pm, RedGrittyBrick <RedGrittyBr...(a)spamweary.invalid> > wrote: > > > > > > > On 28/06/2010 10:41, gk wrote: > > > > please look at the doc for ResultSet > > > >http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ResultSet.html#TYPE_.... > > > > TYPE_SCROLL_SENSITIVE > > > public static final int TYPE_SCROLL_SENSITIVEThe constant indicating > > > the type for a ResultSet object that is scrollable and generally > > > sensitive to changes made by others. > > > > What it means by "generally sensitive to changes made by others" ? I > > > don't get this part. > > > For general questions of this sort, you'll often get an adequate answer > > by searching using Google or some other search engine: > > >http://en.wikipedia.org/wiki/Cursor_%28databases%29 > > > "Scrollable cursors can potentially access the same row in the result > > set multiple times. Thus, data modifications (insert, update, delete > > operations) from other transactions could have an impact on the result > > set. A cursor can be SENSITIVE or INSENSITIVE to such data > > modifications. A sensitive cursor picks up data modifications impacting > > the result set of the cursor, and an insensitive cursor does not." > > > Note that this is really an SQL question, more than a Java question. > > Sometimes you'll get more relevant answers to DBMS-specific SQL > > questions in an appropriate database newsgroup or forum. > > > -- > > RGB > > Thanks . your post was very much helpful.- Hide quoted text - > > - Show quoted text - However , how does it different from attribute CONCUR_UPDATABLE ? http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ResultSet.html#CONCUR_UPDATABLE If we use CONCUR_UPDATABLE as a ResultSet attribute that too also picks up the updated data ...is not it ? why do we need the SENSITIVE attribute then ?
From: Lew on 28 Jun 2010 08:23
RedGrittyBrick wrote: >> For general questions of this sort, you'll often get an adequate answer >> by searching using Google or some other search engine: >> >> http://en.wikipedia.org/wiki/Cursor_%28databases%29 >> >> "Scrollable cursors can potentially access the same row in the result >> set multiple times. Thus, data modifications (insert, update, delete >> operations) from other transactions could have an impact on the result >> set. A cursor can be SENSITIVE or INSENSITIVE to such data >> modifications. A sensitive cursor picks up data modifications impacting >> the result set of the cursor, and an insensitive cursor does not." >> >> Note that this is really an SQL question, more than a Java question. >> Sometimes you'll get more relevant answers to DBMS-specific SQL >> questions in an appropriate database newsgroup or forum. gk wrote: >> -- >> RGB Please do not quote sigs. > Thanks . your post was very much helpful. Particularly the part where he suggested Google or other search and Wikipedia. -- Lew |