[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241642#comment-17241642
]
Richard N. Hillegas commented on DERBY-7091:
Glad that you found a workaround. Thanks for
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241150#comment-17241150
]
Larry Melvin Lemons commented on DERBY-7091:
Well I found a work around. Shut down the
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236964#comment-17236964
]
Richard N. Hillegas commented on DERBY-7091:
Parsing and formatting of timestamps is handled
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236844#comment-17236844
]
Larry Melvin Lemons commented on DERBY-7091:
OK. In your reply above, Anurag Shekhar is
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236772#comment-17236772
]
Richard N. Hillegas commented on DERBY-7091:
Derby does not manipulate timestamp values.
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236601#comment-17236601
]
Larry Melvin Lemons commented on DERBY-7091:
But that makes querying the database for a
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235574#comment-17235574
]
Richard N. Hillegas commented on DERBY-7091:
Thanks for that explanation of the problem you
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235064#comment-17235064
]
Larry Melvin Lemons commented on DERBY-7091:
And yet it doesn't say anything about it
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234993#comment-17234993
]
Richard N. Hillegas commented on DERBY-7091:
The SQL Standard TIMESTAMP type does not include
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234906#comment-17234906
]
Larry Melvin Lemons commented on DERBY-7091:
Unfortunately it doesn't for ALL timezones, only
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234806#comment-17234806
]
Larry Melvin Lemons commented on DERBY-7091:
Then how do you represent UTC times in the
On 11/16/20 10:41 PM, Anurag Shekhar wrote:
2017-03-12 02:48:00.000
Thanks for pointing that out, Anurag!
:48:00.000 are non-existent times. The standard
notation for those instants are 2017-03-12 03:00:00.000 and 2017-03-12
03:48:00.000 respectively:
http://apache-database.10148.n7.nabble.com/jira-Commented-DERBY-7091-Times-Inserted-Incorrectly-Around-Daylight-Savings-Time-Change-in-Spring-td151535.
Hi
ij> SELECT * FROM t ORDER BY key_col;
KEY_COL|DESC_COL |TS_STRING |TS
---
1 |NULL |2017-03-12 01:48:00.000
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232951#comment-17232951
]
Larry Melvin Lemons commented on DERBY-7091:
I added a simple program that demonstrates the
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232170#comment-17232170
]
Richard N. Hillegas commented on DERBY-7091:
Thanks for logging this odd behavior. The
[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232159#comment-17232159
]
Bryan Pendleton commented on DERBY-7091:
Can you attach a simple program that demonstrates the
17 matches
Mail list logo
