db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Boynes <jboy...@apache.org>
Subject Re: [jira] Commented: (DERBY-194) getPrecision() on TIME and TIMESTAMP is zero
Date Mon, 04 Apr 2005 16:15:47 GMT
A B (JIRA) wrote:
> [
> http://issues.apache.org/jira/browse/DERBY-194?page=comments#action_62077
> ]
> 
> A B commented on DERBY-194: ---------------------------
> 
> I (Army) have been looking at a couple of database metadata issues in
> Derby (as a follow-up to DERBY-107), and this is one that I too have
> noticed.
> 
> Fix is to change the "setTypeIdSpecificInstanceVariables()" method in
> org/apache/derby/iapi/types/TypeId.java to set the "maxMaxWidth"
> variable to be the correct value (namely, 8 for TIME (hh:mm:ss) and
> 26 for TIMESTAMP (yyyy-mm-dd hh:mm:ss.ffffff)).
> 
> Unless someone wants to create a specific patch for this, I'll submit
> this fix as part of another patch that I'm writing--one that will
> make Derby metadata return the correct value for the BUFFER_LENGTH
> field for  builtin (including datetime) types.  See the thread here
> for more on the BUFFER_LENGTH issue:

Please make a separate patch for it - it makes it easier to track the 
changes back to the relevant JIRA issues.

If we do this consistently we can autogenerate release notes from Jira 
reports saving the release manager a lot of work :-)

--
Jeremy

Mime
View raw message