Menu

#413 clock scan Bug

obsolete: 8.2
closed-wont-fix
nobody
2
2001-04-18
2000-10-26
Anonymous
No

OriginalBugID: 2843 Bug
Version: 8.2
SubmitDate: '1999-09-20'
LastModified: '1999-09-20'
Severity: MED
Status: Closed
Submitter: techsupp
ChangedBy: hobbs
OS: Other
OSVersion: Linux SuSE 6.2
Machine: NA
FixedDate: '2000-10-25'
ClosedDate: '1999-09-20'

Name:
Marc Ziegenhagen

ReproducibleScript:
I woud like to work with the clock scan function but it those not right.
I like to convert Dates older than 1970 but this not works correctly.
The Date 8. April 1968 does not work, but the 8. April 1969 works and
also the 8. April 1988.
An other Question what it brings back when the systemdate is in 2000 or
higher is the default of
the value who will be added to 2 digit-Year 2000 or 1900? In the manual
it's writen 1900!

ObservedBehavior:
clock scan "4/8/68 0:0:0" ==> unable to convert date-time string "4/8/68
0:0:0"
clock scan "4/8/69 0:0:0" ==> -23158800
clock scan "4/8/88 0:0:0" ==> 576453600

DesiredBehavior:
I will see a minus value like the other one.

This is not a bug. The epoch on Unix starts in 1969, and the
time function allows dates in that year, but not earlier. You
see the negative number for dates before Dec 31, 1969 (the actual
day of the epoch). You need to build a more generic layer to
support dates outside of what Unix normally provides. For Y2K
info, see http://www.scriptics.com/Y2K.html (Tcl is Y2K safe).
-- 09/20/1999 hobbs

Discussion

  • Brent B. Welch

    Brent B. Welch - 2000-10-26
    • priority: 5 --> 2
    • status: open --> closed-fixed
     
  • Don Porter

    Don Porter - 2001-04-18
    • labels: 104246 --> 06. Time Measurement
    • status: closed-fixed --> closed-wont-fix
     
MongoDB Logo MongoDB