[
https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2280:
---------------------------------
Attachment: getTypeInfo.html
Attaching getTypeInfo.html, the output of the embedded call to
DatabaseMetaData.getTypeInfo(). I think that BLOB should agree with LONG
VARCHAR FOR BIT DATA and CLOB should agree with LONG VARCHAR. I can think of no
reason that the values should disagree. Here are the values for both LONG
VARCHAR FOR BIT DATA and LONG VARCHAR:
UNSIGNED_ATTRIBUTE = true
AUTO_INCREMENT = false
I suppose the next question is this: is Derby reporting the correct values for
LONG VARCHAR FOR BIT DATA and LONG VARCHAR? The values look right to me.
Certainly the value for AUTO_INCREMENT ought to be non-controversial: none of
these types can be used for identity columns. To me the only other value which
makes sense for UNSIGNED_ATTRIBUTE is NULL. But according to the Java 6 javadoc
for getTypeInfo(), NULL is only allowed for the following columns:
LITERAL_PREFIX
LITERAL_SUFFIX
CREATE_PARAMS
LOCAL_TYPE_NAME
> 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.1.4
> Reporter: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2280.diff, Derby-2280.stat, Derby-2280_v2.diff,
> getTypeInfo.html
>
>
> 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.
