Details
Description
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.
Attachments
Attachments
Issue Links
- relates to
-
DERBY-4626 Timestamp truncated when converted to string with explicit calendar
- Closed
-
DERBY-2602 TIMESTAMP value is truncated when return to client
- Closed
-
DERBY-4625 TIMESTAMP function doesn't accept nanoseconds
- Closed