Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.3.1.4
    • Component/s: Test
    • Labels:
      None
    1. derby-1979.stat
      0.7 kB
      Fernanda Pizzorno
    2. derby-1979.diff
      77 kB
      Fernanda Pizzorno

      Activity

      Hide
      Knut Anders Hatlen added a comment -

      I was curious about why the test only ran in embedded mode since it
      didn't seem to use any features that the client driver doesn't
      support. It turned out that in some error situations embedded aborts
      the execution of the statement, whereas the client raises an exception
      without aborting the statement. I have logged this as DERBY-2017 and
      added a comment about it in the suite method. Committed revision
      469128.

      Show
      Knut Anders Hatlen added a comment - I was curious about why the test only ran in embedded mode since it didn't seem to use any features that the client driver doesn't support. It turned out that in some error situations embedded aborts the execution of the statement, whereas the client raises an exception without aborting the statement. I have logged this as DERBY-2017 and added a comment about it in the suite method. Committed revision 469128.
      Hide
      Dyre Tjeldvoll added a comment -

      I had a quick look at patch and I think it looks good. If I understand correctly, the test only runs in embedded mode, presumably because of the different level of CLOB/BLOB support in the two drivers. I seem to recall someone suggesting that all tests that can only run with one driver should docuement this explicitly. But since this is documented on the Wiki page, I don't see it as important.
      +1 to commit.

      Show
      Dyre Tjeldvoll added a comment - I had a quick look at patch and I think it looks good. If I understand correctly, the test only runs in embedded mode, presumably because of the different level of CLOB/BLOB support in the two drivers. I seem to recall someone suggesting that all tests that can only run with one driver should docuement this explicitly. But since this is documented on the Wiki page, I don't see it as important. +1 to commit.
      Hide
      Fernanda Pizzorno added a comment -

      The attached patch (derby-1979.diff) converts the test jdbcapi/characterStreams.java to Junit.

      A summary of what it tested by this test can be found at: http://wiki.apache.org/db-derby/CharacterStreamTestCoverage.

      I have successfully run suites.All with this patch. Can someone please review it?

      Show
      Fernanda Pizzorno added a comment - The attached patch (derby-1979.diff) converts the test jdbcapi/characterStreams.java to Junit. A summary of what it tested by this test can be found at: http://wiki.apache.org/db-derby/CharacterStreamTestCoverage . I have successfully run suites.All with this patch. Can someone please review it?

        People

        • Assignee:
          Fernanda Pizzorno
          Reporter:
          Fernanda Pizzorno
        • Votes:
          1 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development