Derby
  1. Derby
  2. DERBY-1318

Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: 10.4.2.0
    • Component/s: JDBC, Test
    • Urgency:
      Normal

      Description

      Currently, our DataSources are serializable in order to play well with JNDI. However, we have no upgrade test verifying that DataSource serialization works across release boundaries. We should add this case to our upgrade tests.

      Further recommendations by Dan:

      "I do think though that upgrade testing recently brought into the mainline by Deepa should be enhanced to test:

      • serializing Derby''s data source implementations in 10.1 and seeing it unserializes with 10.2
        (maybe into a BLOB column)
      • making a Reference object out of Derby''s data source implementations in 10.1 and making it into
        an object with 10.2. (if this type of tetsing makes sense for References')"
      1. derby-1318-1a-for_comments.diff
        37 kB
        Kristian Waagan
      2. derby-1318-1a-for_comments.stat
        4 kB
        Kristian Waagan
      3. derby-1318-1b-for_comments.diff
        36 kB
        Kristian Waagan
      4. derby-1318-1b-for_comments.stat
        3 kB
        Kristian Waagan
      5. derby-1318-2a-javadoc_and_build.diff
        3 kB
        Kristian Waagan
      6. serialized-data-sources.zip
        16 kB
        Kristian Waagan

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Rick Hillegas
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development