db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4614) JDBC metadata gives incorrect lengths for timestamps
Date Thu, 02 Sep 2010 11:49:54 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905483#action_12905483
] 

Knut Anders Hatlen commented on DERBY-4614:
-------------------------------------------

I ran the regression tests with the patch, and these three tests failed for me in derbyall:

derbyall/derbyall.fail:lang/compressTable.sql
derbyall/derbyall.fail:lang/specjPlans.sql
derbyall/derbyall.fail:lang/triggerRefClause.sql

It looks like all failures were caused by ij giving more space to timestamp columns, so we
just need to update the master files.

> JDBC metadata gives incorrect lengths for timestamps
> ----------------------------------------------------
>
>                 Key: DERBY-4614
>                 URL: https://issues.apache.org/jira/browse/DERBY-4614
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Rick Hillegas
>            Assignee: C.S. Nirmal J. Fernando
>         Attachments: derby-4614-1.diff, derby-4614-fs.html
>
>
> While looking into DERBY-2602, I noticed that Derby gives the wrong lengths for various
fields in the JDBC metadata for timestamps. I will attach a spec describing what I think should
be done to correct this.

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


Mime
View raw message