Attaching derby-4613-01-ab-correctBehavior.diff. This patch implements the behavior described in the functional spec attached to this issue. This makes the embedded and network drivers treat BOOLEAN values identically provided that both the client and the server are Derby code at version 10.7 or higher. Regression tests passed cleanly for me. Compatibility tests need to be written to verify that clients and servers play well with down-rev partners.
Touches the following files:
Exposes the DRDA and DB2 constants for the BOOLEAN datatype, as described in table 5-11 of section 5.7 (FD:OCA Meta Data Summary) of Volume 1 of version 4 of the DRDA spec.
Server-side logic for determining whether the client-side of the connection is at 10.7 or higher.
Server-side logic for sending BOOLEAN values and their corresponding metadata.
Client-side logic determining whether the server-side of a connection is at 10.7 or higher. I found that I needed this logic in the abstract am package. While I was in there, I moved a number of similar methods out of the concrete net package up into the abstract am package. Ultimately, I think that the am package should be eliminated. See DERBY-4648.
Client-side logic for reading BOOLEAN values and their corresponding metadata.
Changes to the tests to reflect the new behavior of the network client.