[jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

["Saurabh Vyas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470632 ] 

Saurabh Vyas commented on DERBY-2260:
-------------------------------------

This correction in the PRECISION values requires change in DatabaseMetaDataTest.java as the test now checks for correct precision.
This is also implemented in patch for Derby-2558.

NOTE : In future I 'll try and work on all issues independently & not mixing them (like what I did for Derby  2258, 2259 & 2260). My apologies if this caused inconvenience.  

> DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-2260
>                 URL: https://issues.apache.org/jira/browse/DERBY-2260
>             Project: Derby
>          Issue Type: Bug
>    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: Daniel John Debrunner
>         Assigned To: Saurabh Vyas
>            Priority: Minor
>
> PRECISION column for VARCHAR FOR BIT DATA is returned as 32762, but maximum precision is 32672 (6 & 7 swapped).
> ij> create table z (a varchar(32672) for bit data);
> 0 rows inserted/updated/deleted
> ij> create table z2(a varchar(32673) for bit data);
> ERROR 42611: The length, precision, or scale attribute for column, or type mapping 'VARCHAR (32673) FOR BIT DATA' is not valid.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.