[
https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490386
]
A B commented on DERBY-2280:
----------------------------
I think the relevant comment from DERBY-2258 is:
"Given that the JDBC API does not say that these "may be null", I tend to agree
with Knut Anders on this, too. I did find it odd that CLOB and BLOB have "null"
for these values while the other char types have "TRUE" and "FALSE",
respectively. Is that a bug/inconsistency that should be fixed (as a separate
issue)?"
So I think the goal of this issue should be to make CLOB and BLOB agree with
the other char and "for bit data" types. In other words, my guess is that CLOB
and BLOB should return "TRUE" for UNSIGNED_ATTRIBUTE (as Kathey suggested) and
"FALSE" for AUTO_INCREMENT since that's what we return for CHAR, VARCHAR, LONG
VARCHAR, and for all of the "FOR BIT DATA" types as well.
Also note: I think value of UNSIGNED_ATTRIBUTE should be "TRUE" for the XML
datatype, as well (it is currently "FALSE" as of DERBY-2258).
> DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column
> returns incorrect information for BLOB & CLOB data type
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2280
> URL: https://issues.apache.org/jira/browse/DERBY-2280
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 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.0.0
> Reporter: Saurabh Vyas
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2280.diff, Derby-2280.stat
>
>
> getTypeInfo() method should return FALSE for UNSIGNED_ATTRIBUTE and
> AUTO_INCREMENT in case of BLOB & CLOB data type.
> Currently it returns NULL value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
