db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-369) Document differences between Embedded and Network Server for Updatable ResultSets functionality
Date Fri, 17 Jun 2005 18:00:57 GMT
Document differences between Embedded and Network Server for Updatable ResultSets functionality
-----------------------------------------------------------------------------------------------

         Key: DERBY-369
         URL: http://issues.apache.org/jira/browse/DERBY-369
     Project: Derby
        Type: Sub-task
  Components: Documentation  
    Versions: 10.1.0.0    
    Reporter: Mamta A. Satoor
 Assigned to: Jeff Levitt 
     Fix For: 10.1.0.0


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


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message