[
https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496632
]
A B commented on DERBY-2280:
----------------------------
There is a test failure, yes. I think Saurabh was waiting for a reply to the
latest comment on DERBY-2307 regarding how he should proceed (i.e. is the new
behavior correct or incorrect?).
Saurabh, given the lack of comments one way or the other re: DERBY-2307, I
think it would be okay to change the "JDBC_COLUMN_NULLABILITY_DERBY_2307" array
in DatabaseMetaDataTest to reflect that UNSIGNED_ATTRIBUTE and AUTO_INCREMENT
now have a "false" nullability, which should (I think?) make that test pass.
The JDBC API does *not* include the words "may be null" next to those columns,
so I think returning "false" as nullability seems reasonable. It would be good
to verify that on derby-dev, though, with a direct email (in case people are
filtering out the Jira emails).
To answer Kathey's question, I would think that Yes, the patch available box
can be unchecked for now (until the test is updated to pass). Do you agree,
Saurabh?
> 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, Derby-2280_v2.diff
>
>
> 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.
