[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4614:
---------------------------------
Attachment: derby-4614-02-ab-compatProblem.diff
Attaching derby-4614-02-ab-compatProblem.diff. This fixes the problem case
which Knut found. I will run regression tests.
This patch makes the trunk client and server use 26 character timestamps if the
other end of the connection does not expect nanosecond precision.
I have tested Knut's problem case in the following scenarios:
1) Client = trunk; server = trunk
2) Client = trunk; server = 10.5
3) Client = trunk; server = 10.6
4) Client = 10.6; server = trunk
5) Client = 10.5; server = trunk
I have successfully run the compatibility tests on Java 6 using clients and
servers at the following rev levels:
trunk
10.4.2.1
10.6.1.0
Touches the following files:
-------------
M java/engine/org/apache/derby/iapi/reference/DRDAConstants.java
Introduced a constant to represent the old 26 character timestamp length.
-------------
M java/drda/org/apache/derby/impl/drda/AppRequester.java
M java/client/org/apache/derby/client/am/DateTime.java
Use the old length if the other side of the connection expects it.
> 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.7.1.2, 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: d4614_hang.java, derby-4614-01-aa-warmedUp.diff,
> derby-4614-01-ab-warmedUp.diff, derby-4614-01-ac-warmedUp.diff,
> derby-4614-01-ad-warmedUp.diff, derby-4614-01-ae-warmedUp.diff,
> derby-4614-02-ab-compatProblem.diff, derby-4614-1.diff, derby-4614-fs.html,
> derby_4614-2.diff, releaseNote.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.
