Derby
  1. Derby
  2. DERBY-310

Document and/or change Derby client code to match behavior with Embedded driver where possible.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: 10.6.1.0
    • Component/s: Documentation, JDBC
    • Labels:
      None

      Description

      [NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]

      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

        Issue Links

        There are no Sub-Tasks for this issue.

          Activity

          Satheesh Bandaram created issue -
          David Van Couvering made changes -
          Field Original Value New Value
          Link This issue is blocked by DERBY-211 [ DERBY-211 ]
          David Van Couvering made changes -
          Link This issue is blocked by DERBY-254 [ DERBY-254 ]
          Hide
          David Van Couvering added a comment -

          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...

          Show
          David Van Couvering added a comment - 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...
          Hide
          Satheesh Bandaram added a comment -

          Derby-310 is trying to compile all list of known issues.

          Show
          Satheesh Bandaram added a comment - Derby-310 is trying to compile all list of known issues.
          Satheesh Bandaram made changes -
          Link This issue incorporates DERBY-307 [ DERBY-307 ]
          Hide
          Jeff Levitt added a comment -

          Attached is a zip containing a patch and sample html output for review. The patch creates a new page called "Updatable resultsets" in the admin guide under "Differences between running Derby in embedded mode and using the network server". The page includes the differences listed by Mamta. A review would be appreciated. Thanks!

          Show
          Jeff Levitt added a comment - Attached is a zip containing a patch and sample html output for review. The patch creates a new page called "Updatable resultsets" in the admin guide under "Differences between running Derby in embedded mode and using the network server". The page includes the differences listed by Mamta. A review would be appreciated. Thanks!
          Jeff Levitt made changes -
          Attachment derby310.zip [ 12310798 ]
          Hide
          David Van Couvering added a comment -

          Here are my thoughts on this:

          • Shouldn't this be in a separate section? There are differences between the embedded and network client beyond updatable result sets.
          • There are other items linked to this JIRA id that describe other differences
          • I don't think anybody has run a full test of all the embedded tests against the client to see what doesn't work. You should probably say there may be other differences that have not yet been identified
          • I thought there were some differences around XA, or did Kathey and co fix all of these?
          • The format that the html generator is creating is a bit klunky. These same issues existed in the error messages
            document I reviewed. In particular
          • The line spacing is awkward; often there is no spacing between paragraphs
          • The table header should be in bold, it's hard to tell it's a table header
          • The header should be "Updatable Result Sets" not "Updatable resultsets"

          Thanks,

          David

          Show
          David Van Couvering added a comment - Here are my thoughts on this: Shouldn't this be in a separate section? There are differences between the embedded and network client beyond updatable result sets. There are other items linked to this JIRA id that describe other differences I don't think anybody has run a full test of all the embedded tests against the client to see what doesn't work. You should probably say there may be other differences that have not yet been identified I thought there were some differences around XA, or did Kathey and co fix all of these? The format that the html generator is creating is a bit klunky. These same issues existed in the error messages document I reviewed. In particular The line spacing is awkward; often there is no spacing between paragraphs The table header should be in bold, it's hard to tell it's a table header The header should be "Updatable Result Sets" not "Updatable resultsets" Thanks, David
          Hide
          Jeff Levitt added a comment -

          Thanks for the feedback David,

          I'll try to respond to each of your comments...

          • In regards to a separate section, this document has been placed as a subsection to a larger section called "Differences between running Derby in embedded mode and using the network server." There are other subsections to that main section that talk about other differences that dont have to do with updatable result sets. So I'm not sure what you mean by it should have its own section. Take a look at that area of the Server Admin Guide as it exists now:
            http://incubator.apache.org/derby/docs/adminguide/cadminapps.html
          • Of the other items linked to this issue, both were unsettled. I wanted to at least get the differences about updatable result sets into the docs.
          • I agree that we should say something about not every difference has been identified and that there could be more. Perhaps I should add that to the "Differences between running Derby in embedded mode and using the network server" page instead of this updatable result sets differences page, since it should be a broader statement than this one subsection. I'll make a new patch. Thanks!
          • If Kathy has input on XA differences, I'd be happy to doc those too. Again, if it comes down to a timing issue in terms of whether we get some or none of these documented in 10.1, I think it would be better to at least have added what we have than nothing at all.
          • I think the formatting issues have to do with the fact that we don't have a css file to format our output to look nicer. Perhaps we can open a JIRA issue as an improvement and someone could write one or find one we can use. Such formatting issues as making the titles of tables bold could easily be accomplished with a good css file. I'd be happy to look into whether the DITA toolkit has some sort of option that we can specify to put css specifications directly into the files during transform. I honestly haven't worked too much with them to know the details, but I'm sure that is how its done. I'm not optimistic that we could have something together before 10.1 though.
          • I'll fix the header as you suggested with my new patch.

          I'll hold off on the patch for awhile to see if anyone has any other comments, suggestions, or requests due to some of the issues David has raised. Thanks again for the feedback!

          Show
          Jeff Levitt added a comment - Thanks for the feedback David, I'll try to respond to each of your comments... In regards to a separate section, this document has been placed as a subsection to a larger section called "Differences between running Derby in embedded mode and using the network server." There are other subsections to that main section that talk about other differences that dont have to do with updatable result sets. So I'm not sure what you mean by it should have its own section. Take a look at that area of the Server Admin Guide as it exists now: http://incubator.apache.org/derby/docs/adminguide/cadminapps.html Of the other items linked to this issue, both were unsettled. I wanted to at least get the differences about updatable result sets into the docs. I agree that we should say something about not every difference has been identified and that there could be more. Perhaps I should add that to the "Differences between running Derby in embedded mode and using the network server" page instead of this updatable result sets differences page, since it should be a broader statement than this one subsection. I'll make a new patch. Thanks! If Kathy has input on XA differences, I'd be happy to doc those too. Again, if it comes down to a timing issue in terms of whether we get some or none of these documented in 10.1, I think it would be better to at least have added what we have than nothing at all. I think the formatting issues have to do with the fact that we don't have a css file to format our output to look nicer. Perhaps we can open a JIRA issue as an improvement and someone could write one or find one we can use. Such formatting issues as making the titles of tables bold could easily be accomplished with a good css file. I'd be happy to look into whether the DITA toolkit has some sort of option that we can specify to put css specifications directly into the files during transform. I honestly haven't worked too much with them to know the details, but I'm sure that is how its done. I'm not optimistic that we could have something together before 10.1 though. I'll fix the header as you suggested with my new patch. I'll hold off on the patch for awhile to see if anyone has any other comments, suggestions, or requests due to some of the issues David has raised. Thanks again for the feedback!
          Hide
          Mamta A. Satoor added a comment -

          I looked at the page with Updatable ResultSet differences and it looks good.

          Show
          Mamta A. Satoor added a comment - I looked at the page with Updatable ResultSet differences and it looks good.
          Kathey Marsden made changes -
          Description 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)
          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
          Environment
          Hide
          Jeff Levitt added a comment -

          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.

          Show
          Jeff Levitt added a comment - 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.
          Hide
          David Van Couvering added a comment -

          Sorry I didn't respond sooner..

          JACK SAID

          In regards to a separate section, this document has been placed as a subsection to a larger section called
          "Differences between running Derby in embedded mode and using the network server." There are other
          subsections to that main section that talk about other differences that dont have to do with updatable result sets. So I'm not sure what you mean by it should have its own section. Take a look at that area of the Server Admin Guide as it exists now:
          http://incubator.apache.org/derby/docs/adminguide/cadminapps.html

          MY RESPONSE:

          OK, I didn't know that

          JACK SAID

          • Of the other items linked to this issue, both were unsettled. I wanted to at least get the differences about updatable result sets into the docs.

          MY RESPONSE

          OK, I thought this was the place where differences were documented

          JACK SAID

          • I agree that we should say something about not every difference has been identified and that there could be more. Perhaps I should add that to the "Differences between running Derby in embedded mode and using the network server" page instead of this updatable result sets differences page, since it should be a broader statement than this one subsection. I'll make a new patch. Thanks!

          MY RESPONSE

          Great, sounds good

          JACK SAID

          • If Kathy has input on XA differences, I'd be happy to doc those too. Again, if it comes down to a timing issue in terms of whether we get some or none of these documented in 10.1, I think it would be better to at least have added what we have than nothing at all.

          MY RESPONSE

          ok

          JACK SAID

          • I think the formatting issues have to do with the fact that we don't have a css file to format our output to look nicer. Perhaps we can open a JIRA issue as an improvement and someone could write one or find one we can use. Such formatting issues as making the titles of tables bold could easily be accomplished with a good css file. I'd be happy to look into whether the DITA toolkit has some sort of option that we can specify to put css specifications directly into the files during transform. I honestly haven't worked too much with them to know the details, but I'm sure that is how its done. I'm not optimistic that we could have something together before 10.1 though.

          MY RESPONSE

          Hm. I am uncomfortable going out with the release when the HTML is so clunky. I don't know how hard it is to set up a css file, but it seems like if we're trying to get people interested in using Derby, having docs that look funky does not send out a good message to interested but hesitant new users.

          JACK SAID

          • I'll fix the header as you suggested with my new patch.

          MY RESPONSE

          ok, great
          I'll hold off on the patch for awhile to see if anyone has any other comments, suggestions, or requests due to some of the issues David has raised. Thanks again for the feedback!

          Show
          David Van Couvering added a comment - Sorry I didn't respond sooner.. JACK SAID In regards to a separate section, this document has been placed as a subsection to a larger section called "Differences between running Derby in embedded mode and using the network server." There are other subsections to that main section that talk about other differences that dont have to do with updatable result sets. So I'm not sure what you mean by it should have its own section. Take a look at that area of the Server Admin Guide as it exists now: http://incubator.apache.org/derby/docs/adminguide/cadminapps.html MY RESPONSE: OK, I didn't know that JACK SAID Of the other items linked to this issue, both were unsettled. I wanted to at least get the differences about updatable result sets into the docs. MY RESPONSE OK, I thought this was the place where differences were documented JACK SAID I agree that we should say something about not every difference has been identified and that there could be more. Perhaps I should add that to the "Differences between running Derby in embedded mode and using the network server" page instead of this updatable result sets differences page, since it should be a broader statement than this one subsection. I'll make a new patch. Thanks! MY RESPONSE Great, sounds good JACK SAID If Kathy has input on XA differences, I'd be happy to doc those too. Again, if it comes down to a timing issue in terms of whether we get some or none of these documented in 10.1, I think it would be better to at least have added what we have than nothing at all. MY RESPONSE ok JACK SAID I think the formatting issues have to do with the fact that we don't have a css file to format our output to look nicer. Perhaps we can open a JIRA issue as an improvement and someone could write one or find one we can use. Such formatting issues as making the titles of tables bold could easily be accomplished with a good css file. I'd be happy to look into whether the DITA toolkit has some sort of option that we can specify to put css specifications directly into the files during transform. I honestly haven't worked too much with them to know the details, but I'm sure that is how its done. I'm not optimistic that we could have something together before 10.1 though. MY RESPONSE Hm. I am uncomfortable going out with the release when the HTML is so clunky. I don't know how hard it is to set up a css file, but it seems like if we're trying to get people interested in using Derby, having docs that look funky does not send out a good message to interested but hesitant new users. JACK SAID I'll fix the header as you suggested with my new patch. MY RESPONSE ok, great I'll hold off on the patch for awhile to see if anyone has any other comments, suggestions, or requests due to some of the issues David has raised. Thanks again for the feedback!
          Kathey Marsden made changes -
          Comment [ 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
          ]
          David Van Couvering made changes -
          Link This issue incorporates DERBY-461 [ DERBY-461 ]
          Dag H. Wanvik made changes -
          Link This issue relates to DERBY-477 [ DERBY-477 ]
          Hide
          Satheesh Bandaram added a comment -

          Linking this to DERBY-310, though in this case, we probably want to change the embedded driver to match network client.

          Show
          Satheesh Bandaram added a comment - Linking this to DERBY-310 , though in this case, we probably want to change the embedded driver to match network client.
          Satheesh Bandaram made changes -
          Link This issue incorporates DERBY-501 [ DERBY-501 ]
          Oyvind Bakksjo made changes -
          Link This issue incorporates DERBY-31 [ DERBY-31 ]
          Kathey Marsden made changes -
          Link This issue incorporates DERBY-525 [ DERBY-525 ]
          Hide
          Sunitha Kambhampati added a comment -

          link DERBY-572 to DERBY-310, to keep track of client/embedded differences.

          Show
          Sunitha Kambhampati added a comment - link DERBY-572 to DERBY-310 , to keep track of client/embedded differences.
          Sunitha Kambhampati made changes -
          Link This issue incorporates DERBY-572 [ DERBY-572 ]
          Tomohito Nakayama made changes -
          Link This issue incorporates DERBY-596 [ DERBY-596 ]
          Satheesh Bandaram made changes -
          Link This issue is related to DERBY-142 [ DERBY-142 ]
          Hide
          Satheesh Bandaram added a comment -

          isReadOnly() and possibly isWriteOnly() don't match behavior between DerbyClient and embedded.

          Show
          Satheesh Bandaram added a comment - isReadOnly() and possibly isWriteOnly() don't match behavior between DerbyClient and embedded.
          Deepa Remesh made changes -
          Link This issue incorporates DERBY-638 [ DERBY-638 ]
          Oyvind Bakksjo made changes -
          Link This issue incorporates DERBY-694 [ DERBY-694 ]
          Kathey Marsden made changes -
          Type Bug [ 1 ] Improvement [ 4 ]
          Mamta A. Satoor made changes -
          Link This issue incorporates DERBY-911 [ DERBY-911 ]
          Hide
          Mamta A. Satoor added a comment -

          Linking Derby-911(Connection.setReadOnly is a no-op in Network Client but works fine with embedded driver) to Derby-310(Document and/or change Derby client code to match behavior with Embedded driver where possible.)

          Show
          Mamta A. Satoor added a comment - Linking Derby-911(Connection.setReadOnly is a no-op in Network Client but works fine with embedded driver) to Derby-310(Document and/or change Derby client code to match behavior with Embedded driver where possible.)
          Mamta A. Satoor made changes -
          Link This issue incorporates DERBY-931 [ DERBY-931 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-965 [ DERBY-965 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-1098 [ DERBY-1098 ]
          Deepa Remesh made changes -
          Link This issue incorporates DERBY-1267 [ DERBY-1267 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-1312 [ DERBY-1312 ]
          Deepa Remesh made changes -
          Link This issue incorporates DERBY-1370 [ DERBY-1370 ]
          Kathey Marsden made changes -
          Link This issue incorporates DERBY-1371 [ DERBY-1371 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-1484 [ DERBY-1484 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-1493 [ DERBY-1493 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-1494 [ DERBY-1494 ]
          Andrew McIntyre made changes -
          Link This issue relates to DERBY-1501 [ DERBY-1501 ]
          Andrew McIntyre made changes -
          Link This issue relates to DERBY-1500 [ DERBY-1500 ]
          Tomohito Nakayama made changes -
          Link This issue incorporates DERBY-1610 [ DERBY-1610 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-1516 [ DERBY-1516 ]
          Kristian Waagan made changes -
          Link This issue incorporates DERBY-1657 [ DERBY-1657 ]
          Kristian Waagan made changes -
          Link This issue incorporates DERBY-1658 [ DERBY-1658 ]
          Bernt M. Johnsen made changes -
          Link This issue incorporates DERBY-2064 [ DERBY-2064 ]
          Bernt M. Johnsen made changes -
          Link This issue incorporates DERBY-2065 [ DERBY-2065 ]
          Bernt M. Johnsen made changes -
          Link This issue incorporates DERBY-2084 [ DERBY-2084 ]
          Øystein Grøvlen made changes -
          Link This issue incorporates DERBY-2113 [ DERBY-2113 ]
          Jean T. Anderson made changes -
          Link This issue is related to DERBY-2301 [ DERBY-2301 ]
          Andrew McIntyre made changes -
          Link This issue incorporates DERBY-1440 [ DERBY-1440 ]
          Kathey Marsden made changes -
          Link This issue incorporates DERBY-2423 [ DERBY-2423 ]
          Kathey Marsden made changes -
          Link This issue incorporates DERBY-2453 [ DERBY-2453 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-2531 [ DERBY-2531 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-2532 [ DERBY-2532 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-728 [ DERBY-728 ]
          Kathey Marsden made changes -
          Link This issue incorporates DERBY-2601 [ DERBY-2601 ]
          Kristian Waagan made changes -
          Link This issue incorporates DERBY-2652 [ DERBY-2652 ]
          Hide
          Kristian Waagan added a comment -

          Linked DERBY-2652 to document different behavior when writing to Clob with the stream returned by setCharacterStream.

          Show
          Kristian Waagan added a comment - Linked DERBY-2652 to document different behavior when writing to Clob with the stream returned by setCharacterStream.
          A B made changes -
          Link This issue incorporates DERBY-2653 [ DERBY-2653 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-2651 [ DERBY-2651 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-2692 [ DERBY-2692 ]
          Kristian Waagan made changes -
          Link This issue incorporates DERBY-2771 [ DERBY-2771 ]
          Dag H. Wanvik made changes -
          Link This issue incorporates DERBY-3114 [ DERBY-3114 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-3171 [ DERBY-3171 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-3436 [ DERBY-3436 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-3851 [ DERBY-3851 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-3853 [ DERBY-3853 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-3856 [ DERBY-3856 ]
          Kristian Waagan made changes -
          Link This issue incorporates DERBY-3898 [ DERBY-3898 ]
          Knut Anders Hatlen made changes -
          Link This issue incorporates DERBY-160 [ DERBY-160 ]
          Hide
          Kathey Marsden added a comment -

          I think now that we have the client/embedded differences checkbox, we should just verify that the linked issues have the box checked and close this issue. Does that sound ok?

          Show
          Kathey Marsden added a comment - I think now that we have the client/embedded differences checkbox, we should just verify that the linked issues have the box checked and close this issue. Does that sound ok?
          Hide
          Dag H. Wanvik added a comment -

          +1

          Show
          Dag H. Wanvik added a comment - +1
          Hide
          Knut Anders Hatlen added a comment -

          All open issues linking to this issue have the Embedded/Client difference box checked. Resolving.

          Show
          Knut Anders Hatlen added a comment - All open issues linking to this issue have the Embedded/Client difference box checked. Resolving.
          Knut Anders Hatlen made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Dag H. Wanvik made changes -
          Description 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
          [NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]

          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
          Yun Lee made changes -
          Link This issue incorporates DERBY-4767 [ DERBY-4767 ]
          Yun Lee made changes -
          Link This issue incorporates DERBY-4777 [ DERBY-4777 ]
          Yun Lee made changes -
          Link This issue incorporates DERBY-4778 [ DERBY-4778 ]
          Kathey Marsden made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Kathey Marsden made changes -
          Affects Version/s 10.6.1.0 [ 12313727 ]
          Affects Version/s 10.1.1.0 [ 10993 ]
          Kathey Marsden made changes -
          Fix Version/s 10.6.1.0 [ 12313727 ]
          Gavin made changes -
          Link This issue incorporates DERBY-307 [ DERBY-307 ]
          Gavin made changes -
          Link This issue incorporates DERBY-307 [ DERBY-307 ]
          Gavin made changes -
          Workflow jira [ 42846 ] Default workflow, editable Closed status [ 12802491 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Satheesh Bandaram
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development