[DERBY-370] Document differences between Embedded and Network Server for Updatable ResultSets functionality

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.1.1.0
• Component/s: Documentation
• Assignee: Jeff Levitt
• Reporter: Mamta A. Satoor
• Created: 18/Jun/05 02:47
• Updated: 21/Jun/05 03:08
• Resolved: 21/Jun/05 03:08

Description

The functionality of updatable resultset for Network Server is similar to what Embedded Derby supports, with the exception of following differences
1)DNC requires that there be at least one column in the select list from the target table.
eg select 1, 2 from t1 for update of c11 will fail in Network Server because driver looks at both the columns in the select list and it can't determine the target table for update/delete looking at those columns' metadata. This is not required by embedded driver. There is test for this (Positive Test2 in updatableResultSet.java).
2)Embedded driver allows Statement name change when there is an open resultset on that statement object. DNC driver does not supported that. (Positive Test8a and Test8b in updatableResultSet.java )
3)(Positive Test20) Embedded driver allows updateString on SMALLINT, INTEGER, BIGINT, DECIMAL datatypes. DNC doesn't.
Embedded driver support updateBytes on CHAR, VARCHAR, LONG VARCHAR datatypes. DNC doesn't
Embedded driver support updateTime on TIMESTAMP datatypes. DNC doesn't
Embedded driver supports updateObject with null value. DNC doesn't
DNC does not support updateClob and updateBlob