You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2005/06/17 20:00:56 UTC

[jira] Created: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Document differences between Embedded and Network Server for Updatable ResultSets functionality
-----------------------------------------------------------------------------------------------

         Key: DERBY-370
         URL: http://issues.apache.org/jira/browse/DERBY-370
     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


[jira] Commented: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-370?page=comments#action_12313957 ] 

Mamta A. Satoor commented on DERBY-370:
---------------------------------------

Jeff, the page looks good. Just one thing, can you change the hading to "Updatable Result Sets" rather than "Updatable result sets". That's how it is documented in JDBC Tutorial at javasoft.

> Document differences between Embedded and Network Server for Updatable ResultSets functionality
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-370
>          URL: http://issues.apache.org/jira/browse/DERBY-370
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions: 10.1.1.0
>     Reporter: Mamta A. Satoor
>     Assignee: Jeff Levitt
>      Fix For: 10.1.1.0
>  Attachments: derby370.zip
>
> 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


[jira] Commented: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-370?page=comments#action_12314066 ] 

Mamta A. Satoor commented on DERBY-370:
---------------------------------------

It looks good now. Thanks for working on it.

> Document differences between Embedded and Network Server for Updatable ResultSets functionality
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-370
>          URL: http://issues.apache.org/jira/browse/DERBY-370
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions: 10.1.1.0
>     Reporter: Mamta A. Satoor
>     Assignee: Jeff Levitt
>      Fix For: 10.1.1.0
>  Attachments: derby370revised.zip
>
> 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


[jira] Closed: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-370?page=all ]
     
Jean T. Anderson closed DERBY-370:
----------------------------------

    Resolution: Fixed

Committed, revision 191526, Jeff Levitt's patch that documents the differences between Embedded and Network Server for Updatable ResultSets. Modified files:
$ svn status
M      src/adminguide/derbyadmin.ditamap
M      src/adminguide/cadminapps.dita
A      src/adminguide/radminappsresultsetdiffs.dita



> Document differences between Embedded and Network Server for Updatable ResultSets functionality
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-370
>          URL: http://issues.apache.org/jira/browse/DERBY-370
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions: 10.1.1.0
>     Reporter: Mamta A. Satoor
>     Assignee: Jeff Levitt
>      Fix For: 10.1.1.0
>  Attachments: derby370revised.zip
>
> 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


[jira] Updated: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-370?page=all ]

Jeff Levitt updated DERBY-370:
------------------------------

    Attachment: derby370revised.zip

All set Mamta,  the attached patch capitalizes "Result Sets" in the title.  Please let me know if it looks good now.  Thanks!

> Document differences between Embedded and Network Server for Updatable ResultSets functionality
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-370
>          URL: http://issues.apache.org/jira/browse/DERBY-370
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions: 10.1.1.0
>     Reporter: Mamta A. Satoor
>     Assignee: Jeff Levitt
>      Fix For: 10.1.1.0
>  Attachments: derby370revised.zip
>
> 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


[jira] Updated: (DERBY-370) Document differences between Embedded and Network Server for Updatable ResultSets functionality

Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-370?page=all ]

Jeff Levitt updated DERBY-370:
------------------------------

    Attachment: derby370.zip

Attached patch creates the updatable result sets differences page as previously described in Derby 310, and also incorporates David's comments concerning the title ("Updatable result sets") and adding the following sentence to the parent topic: "Note that there may be undocumented differences that have not yet been identified."  See the html output for review.

> Document differences between Embedded and Network Server for Updatable ResultSets functionality
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-370
>          URL: http://issues.apache.org/jira/browse/DERBY-370
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions: 10.1.0.0
>     Reporter: Mamta A. Satoor
>     Assignee: Jeff Levitt
>      Fix For: 10.1.0.0
>  Attachments: derby370.zip
>
> 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