Hi Kathey, >>>>> "Kathey" == Kathey Marsden <[EMAIL PROTECTED]> wrote:
Kathey> DERBY-605 currently seems to combine several issues and its summary is Kathey> not that descriptive of what needs implementation. Kathey> I wonder should we have multiple Jira entries that match the Kathey> functionality that needs implementation, one for scrollable ResultSets Kathey> for large objects with client, another for updatable ResultSets for Kathey> large objects with client, etc. Dag what are the various issues that Kathey> you see here, and how would you recommend breaking them up in Jira? Kathey> Kathey> Kathey> FYI, here is the doc page with the differences between client and Kathey> embedded for updatable ResultSets. Kathey> http://db.apache.org/derby/docs/10.1/adminguide/radminappsresultsetdiffs.html Yes, I agree with you, we need to break this (JIRA-605) down in several issues. Here is one way: 1 Forward-only updatable, update: 1.1 c/s: lobs 2 Forward-only updatable, update: 2.1 c/s: remaining problems in update{String, Bytes, Time, Object} 3 Forward-only updatable, insert: now JIRA-100 , could split this in three: 3.1 embedded 3.2 c/s minus lobs 3.3 c/s lobs 4 scrollable updatable sensitive 4.1 embedded (incl lobs) 4.2 c/s minus lobs 4.3 c/s lobs 5 scrollable updatable insensitive (if we ever want do that) I would assume 3.1 and 4.1 could include lobs. We can cross-link all of these to 605. Does 2.1 need splitting? Maybe Mamta can comment on that? Scrollable updatable (4.2) will face the problems under 2.1 also, but any solution should carry over, I suppose. Also, a solution to 1.1 should apply to 4.3. I think it is still ok to keep these as separate issues. I think some exisiting JIRA issues touch on one or more of these (in addition to 100 and 506, I'll start looking...) Once we get these organized I can post an overview on the Wiki. What do you think? Thanks, Dag
