[ http://issues.apache.org/jira/browse/DERBY-310?page=comments#action_66109 ] David Van Couvering commented on DERBY-310: -------------------------------------------
I created links between this item and the bugs Satheesh referred to when he created this item. It seems to make sense that we should continue to set up links (when we find other existing items) or make subtasks for any new items. For example, perhaps all the differences identified by Mamta should be separate subtasks... > Document and/or change Derby client code to match behavior with Embedded > driver where possible. > ----------------------------------------------------------------------------------------------- > > Key: DERBY-310 > URL: http://issues.apache.org/jira/browse/DERBY-310 > Project: Derby > Type: Bug > Components: Documentation, JDBC > Versions: 10.1.0.0 > 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/[EMAIL > PROTECTED]) -- 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
