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] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.
Date Mon, 23 May 2005 20:44:55 GMT
     [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_66100 ]
Mamta A. Satoor commented on DERBY-310:

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

> Document and/or change Derby client code to match behavior with Embedded driver where
> -----------------------------------------------------------------------------------------------
>          Key: DERBY-310
>          URL: http://issues.apache.org/jira/browse/DERBY-310
>      Project: Derby
>         Type: Bug
>   Components: Documentation, JDBC
>     Versions:
>     Reporter: Satheesh Bandaram
>     Priority: Minor

> There are some behavior differences between Derby client and embedded JDBC drivers. Change
Derby client code to match embedded behavior or document some of these differences.
> Please add any differences found to this Jira entry to keep track of known differences.
Some of the known issues are:
> * Derby-211
> * Derby-254
> * Updatable ResultSet differences.
> Kathey Marsden also started this effort to compile known differences.(http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c42854697.1090403@sbcglobal.net%3e)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message