[
https://issues.apache.org/jira/browse/DERBY-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800925#action_12800925
]
Rick Hillegas commented on DERBY-4491:
--------------------------------------
Fixed a sealing violation which surfaced in AssertFailureTest when run against
insane builds: subversion revision 899819. The sealing violation was caused by
the use of the SanityManager which I introduced in Request.java. I don't know
why the SanityManager has been included in the common arm of the codeline if it
gives rise to sealing violations.
While I was in there, I removed the two io classes which I had put in the
common arm. It may be that similar sealing violations will plague them. I
cloned them so that there are now separate client and server copies of
InputStreamUtil.java and DynamicByteArrayOutputStream.java.
I will log a separate issue to track this sealing violation issue. We may need
to reconsider the presence of the SanityManager in the common arm of the
codeline.
> The network client changes UDTs into Strings and returns their type as
> LONGVARBINARY.
> -------------------------------------------------------------------------------------
>
> Key: DERBY-4491
> URL: https://issues.apache.org/jira/browse/DERBY-4491
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0,
> 10.5.1.1, 10.5.2.0, 10.5.3.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-4491-01-ab-networkTransport.diff,
> derby-4491-01-ad-networkTransport.diff
>
>
> This is a pre-existing bug which seems to have been with Derby since the
> beginning. Some of the columns in the system tables (e.g.,
> SYS.SYSALIASES.ALIASINFO) contain objects. If you select these columns:
> 1) In the embedded client you will get the correct results. You will get the
> objects in these columns. In addition, the ResultSetMetaData for these
> columns will correctly report that the columns have type JAVA_OBJECT and will
> give a reasonable type name (the class name for the object in the column).
> 2) However, in the network client, you will get the wrong results.
> ResultSet.getObject() will return Strings rather than the original objects.
> In addition, the ResultSetMetaData for these columns will incorrectly report
> that their type is LONGVARBINARY.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
