[
https://issues.apache.org/jira/browse/DERBY-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593821#comment-13593821
]
Knut Anders Hatlen commented on DERBY-6099:
-------------------------------------------
isCharacterType(int) and isBinaryType(int) left out CLOB and BLOB
intentionally, according to their javadoc comments.
* <p><strong>Note:</strong> <code>CLOB</code> is not compatible with
* <code>String</code>. See tables B-4, B-5 and B-6 in the JDBC 3.0
* Specification.
* <p><strong>Note:</strong> <code>BLOB</code> is not compatible with
* <code>byte[]</code>. See tables B-4, B-5 and B-6 in the JDBC 3.0
* Specification.
> Some DataTypeDescriptor methods may be missing Blob and Clob
> ------------------------------------------------------------
>
> Key: DERBY-6099
> URL: https://issues.apache.org/jira/browse/DERBY-6099
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.3.0
> Reporter: Kathey Marsden
>
> When looking at DERBY-6096, I noticed there are other methods that likely
> should consider CLOB and/or BLOB, for example isCharacterType(int jdbcType)
> does not include CLOB, isBinaryType doesn't include BLOB; normalize() has
> some code that is LONGVARCHAR /LONGVARBINARY specific but that might be no
> longer relevant.
> I do see quite a few bugs in Jira where Blob or Clob was left out of this
> method or that in this file, so it could probably stand a full code review.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
