[#DERBY-194] getPrecision() on TIME and TIMESTAMP is zero

Derby

getPrecision() on TIME and TIMESTAMP is zero

Created: 04/Apr/05 08:15 AM Updated: 08/Jun/05 08:03 AM

Return to search

Component/s:

JDBC

Affects Version/s:

10.0.2.0

Fix Version/s:

10.1.1.0

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
derby-194.patch	2005-06-02 01:51 AM	A B	44 kB
derby-194.stat	2005-06-02 01:51 AM	A B	1.0 kB

Environment:

Windows XP SP1 Professional

Resolution Date:

04/Jun/05 03:51 PM

Description

« Hide

Sun JDBC defines getPrecision() to return either the maximum length or maximum number of digits of the column, or zero for failure (such as the precision is unknown).

http://docs.sun.com/source/816-6105-10/apicola.htm#211083

The DATE field returns 10 characters on a getPrecision() call so why doesn't TIME and TIMESTAMP give a precision length equal to the display length? Just seems inconsistent that DATE would return a precision (as well as all other data types) and not TIME nor TIMESTAMP.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

A B made changes - 27/May/05 06:24 AM

Field	Original Value	New Value
Assignee		A B [ army ]

A B made changes - 02/Jun/05 01:51 AM

Attachment		derby-194.patch [ 20365 ]
Attachment		derby-194.stat [ 20364 ]

A B made changes - 02/Jun/05 01:51 AM

Status

Open [ 1 ]

In Progress [ 3 ]

A B made changes - 03/Jun/05 06:10 AM

Fix Version/s

10.1.0.0 [ 10993 ]

Andrew McIntyre made changes - 04/Jun/05 03:50 PM

Status

In Progress [ 3 ]

Reopened [ 4 ]

Andrew McIntyre made changes - 04/Jun/05 03:51 PM

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

A B made changes - 08/Jun/05 08:03 AM

Status

Resolved [ 5 ]

Closed [ 6 ]