Derby
  1. Derby
  2. DERBY-1252

Old clients with new server return wrong database metadata values for some methods

    Details

    • Urgency:
      Urgent
    • Bug behavior facts:
      Regression

      Description

      With an old client (10.1.1, 10.1.2) accessing a new (10.2) server,
      some metadata calls will return the wrong value for both the JCC and
      the Derby clients:

      deletesAreDetected(TYPE_SCROLL_INSENSITIVE) -> true
      updatedAreDetected(TYPE_SCROLL_INSENSITIVE) -> true
      ownDeletesAreVisible(TYPE_SCROLL_INSENSITIVE) -> true
      ownUpdatesAreVisible(TYPE_SCROLL_INSENSITIVE) -> true

      This happens because these values were changed for the 10.2 with
      the addition of updatable scrollable insensitive result sets (DERBY-775),
      combined with a weakness in the way the client and the server
      cooperates to answer these metadata calls.

      Presently, when the client application invokes these methods, the
      results will be returned by the server without regard to the identity
      of the client, i.e. the 2-tuple

      {JCC or Derby client, client version}

      .
      The values to be returned for the methods in question are based solely
      on the values found in the file metadata_net.properties, which is part
      of the server.

      In general, some database metadata is dependent on the combination of
      the capabilities in the client and the server and the returned values
      should reflect this, which in general implies negotiating (down) to
      values which are correct for the actual combination of client and
      server.

      1. derby1252.diff
        9 kB
        Dag H. Wanvik
      2. derby1252-10.1.diff
        27 kB
        Dag H. Wanvik
      3. derby1252-10.1.stat
        0.6 kB
        Dag H. Wanvik
      4. derby1252.diff
        8 kB
        Dag H. Wanvik
      5. derby1252.stat
        0.4 kB
        Dag H. Wanvik

        Issue Links

          Activity

            People

            • Assignee:
              Dag H. Wanvik
              Reporter:
              Dag H. Wanvik
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development