db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA
Date Tue, 06 Feb 2007 17:15:06 GMT

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

Daniel John Debrunner commented on DERBY-2260:

It was just a safety check to ensure that a NULL value was not being returned for precision.
Probably not required (before the XML changes) since a precision of zero was never returned.
We can assume that a NULL will be returned as zero.

Now with the addition of an XML type you need to test that a NULL value is being returned,
checking for a precision of 0 is not enough. So for the XML case you need ensure that rs.wasNull()
returns true.

> 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:,,,,,,
>            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.

View raw message