[
https://issues.apache.org/jira/browse/DERBY-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236601#comment-17236601
]
Larry Melvin Lemons edited comment on DERBY-7091 at 11/21/20, 7:02 AM:
-----------------------------------------------------------------------
But that makes querying the database for a specific date using the timestamp a
lot harder. I would need to find what that long is to be able to do the query.
Essentially I would need to write a program to query the database if I needed
to get that info. Or use a date String. All workarounds for something that
shouldn't need a workaround. I already created a workaround. I didn't want a
workaround.
So if it is storing the timestamp in a BIGINT field, then I should be able to
just do the inserts and when I query and get the timestamp it should still have
the correct time, so when it is put into a new SQL Date it would have the
correct time, in other words the hours worth of data that had the hour
incremented by an hour would still come be stored in the SQL Date with the
correct time (minus one hour)? If that is the case, then it wouldn't be a
total loss. It would just make manually querying it harder, but querying with
a SQL Date should be fine. Correct?
I just can't understand why it would add an hour during the daylight savings
time switch hour when it doesn't even store a timezone. It should just store
whatever is inserted by default, and not try to do some conversion. Or at
least be consistent and add an hour to ALL times if it is during daylight
savings time, not just for that one hour. It isn't logical.
was (Author: llemons):
But that makes querying the database for a specific date using the timestamp a
lot harder. I would need to find what that long is to be able to do the query.
Essentially I would need to write a program to query the database if I needed
to get that info. Or use a date String. All workarounds for something that
shouldn't need a workaround.
I just can't understand why it would add an hour during the daylight savings
time switch hour when it doesn't even store a timezone. It should just store
whatever is inserted by default, and not try to do some conversion. Or at
least be consistent and add an hour to ALL times if it is during daylight
savings time, not just for that one hour. It isn't logical.
> Times Inserted Incorrectly Around Daylight Savings Time Change in Spring
> ------------------------------------------------------------------------
>
> Key: DERBY-7091
> URL: https://issues.apache.org/jira/browse/DERBY-7091
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.14.2.0
> Environment: Java 14.0.1
> Reporter: Larry Melvin Lemons
> Priority: Critical
> Attachments: Test.java, Timezone_Data_Inconsistencies.odt
>
>
> When inserting date/times into the timestamp field around the daylight
> savings time change in the Spring, the times are inconsistent. I am in/use
> the New York EST/EDT timezone, but the data I am inserting is Standard time
> and not Daylight Savings Time
> All the times are correct up to 1:48AM, then when it inserts 2:00 AM the data
> in the database is 3:00AM. That could be alright if it kept switching the
> time to Daylight Savings Time, however going from inserting 2:48AM and
> getting 3:48AM in the database, when it inserts 3:00AM it shows 3:00AM in the
> database, not the expected 4:00AM. Then in the fall whatever is inserted in
> the database is what shows in the database around the daylight savings time
> switch to standard time. See the attached Open Document Text file for
> examples of what is actually inserted and what is showing in the database.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
