db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Levitt (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 18:46:37 GMT
    [ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_12313913 ] 

Jeff Levitt commented on DERBY-310:

OK, I am going to delete the patch I create for this task and create a new one in Derby 370
with David's suggestions.  That will be for updatable result sets only.  I'll see if I can
create patches independently for any other issues created as well.

> 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.
> This JIRA entry is a top level task for tracking these issues.  Individual subtasks should
be created or existing tasks linked to this Jira entry, but no specific feature content added
here.  Please create subtaks to this Jira entry to track any known differences documentation
issues or tasks needed to investigate this issue.
> 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)
> The Derby community voted that client should match embedded where possible.
> See:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/%3c4298CDDE.5070305@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