db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (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 Fri, 17 Jun 2005 12:58:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313898 ] 

Kathey Marsden commented on DERBY-310:

DERBY-310 should just be a place holder for this larger project of finding, documenting, or
changing Client behaviour.  I think we need two subtasks here now.
1) Document updateable resultSet differences for client and embedded
2) Document known Client/Embedded differences and  future plan for client to match embedded
where possible for the 10.0 release.

If I hear no objections, I will file these two bugs and move off the relevant content later
this morning.  

> 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
>  Attachments: derby310.zip
> 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