[ http://issues.apache.org/jira/browse/DERBY-1252?page=all ]
Dag H. Wanvik updated DERBY-1252:
---------------------------------
Derby Info: [Patch Available, Existing Application Impact, Regression]
(was: [Existing Application Impact, Regression])
> Old clients with new server return wrong database metadata values for some
> methods
> ----------------------------------------------------------------------------------
>
> Key: DERBY-1252
> URL: http://issues.apache.org/jira/browse/DERBY-1252
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client, Network Server
> Affects Versions: 10.1.1.0, 10.1.2.0, 10.1.1.1, 10.1.1.2, 10.1.2.1,
> 10.1.3.0, 10.1.2.2, 10.1.2.3, 10.1.2.4
> Reporter: Dag H. Wanvik
> Assigned To: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
>
> Attachments: derby1252-10.1.diff, derby1252-10.1.stat,
> derby1252.diff, derby1252.diff, derby1252.stat
>
>
> 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.
--
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
