Parse Go time stamp using Go

Question

Go prints time with

time.Now().String()

as

2012-12-18 06:09:18.6155554 +0200 FLEST

or

2009-11-10 23:00:00 +0000 UTC

http://play.golang.org/p/8qwq9U_Ri5

How do I parse it?

I guess FLEST is Finland Latvian Estonian Standard Time I am not in these countries and I guess I can get all kind of time zones. I can't find one unified way or pattern to parse it with time.Parse

I have thought that it's an error in go. Go includes a file lib/time/zoneinfo.zip which "includes" a lot of time zones, but not FLEST. But then I wonder why FLEST has been printed in the first place... — topskip
– topskip, Commented Jan 3, 2013 at 7:12
My Windows 7 PC prints FLEST time zone in log file and same PC can't parse that zone? — Max
– Max, Commented Jan 3, 2013 at 9:06

Jonathan Hall · Accepted Answer · 2020-07-29 09:14:35Z

12

Though time.Parse() accepts a format string such as 2006-01-02 15:04:05 -0700 MST, it may be simpler to use one of the constants defined in time.

const (
    ANSIC       = "Mon Jan _2 15:04:05 2006"
    UnixDate    = "Mon Jan _2 15:04:05 MST 2006"
    RubyDate    = "Mon Jan 02 15:04:05 -0700 2006"
    RFC822      = "02 Jan 06 15:04 MST"
    RFC822Z     = "02 Jan 06 15:04 -0700" // RFC822 with numeric zone
    RFC850      = "Monday, 02-Jan-06 15:04:05 MST"
    RFC1123     = "Mon, 02 Jan 2006 15:04:05 MST"
    RFC1123Z    = "Mon, 02 Jan 2006 15:04:05 -0700" // RFC1123 with numeric zone
    RFC3339     = "2006-01-02T15:04:05Z07:00"
    RFC3339Nano = "2006-01-02T15:04:05.999999999Z07:00"
    Kitchen     = "3:04PM"
    // Handy time stamps.
    Stamp      = "Jan _2 15:04:05"
    StampMilli = "Jan _2 15:04:05.000"
    StampMicro = "Jan _2 15:04:05.000000"
    StampNano  = "Jan _2 15:04:05.000000000"
)

If you're using the strings as a way to store or encode time, (such as with a restrictive encoding format,) you may want to consider using Unix time. That way, you could just store an int64 (or two, if you keep the number of nanoseconds.

edited Jul 29, 2020 at 9:14

Jonathan Hall

80.5k19 gold badges162 silver badges206 bronze badges

answered Dec 30, 2012 at 20:37

Alexander Bauer

11.2k8 gold badges31 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Max Over a year ago

Nothing does not work to parse "2012-12-18 06:09:18.6155554 +0200 FLEST" -

parse error parsing time "2012-12-18 06:09:18.6155554 +0200 FLEST" as "2006-01-02 15:04:05 -0700 MST": cannot parse "FLEST" as "MST"

topskip · Accepted Answer · 2012-12-30 20:23:19Z

10

package main

import (
"fmt"
"time"
)

func main() {
    fmt.Println(time.Now())
    date := "2009-11-10 23:00:00 +0000 UTC"
    t, err := time.Parse("2006-01-02 15:04:05 -0700 MST", date)
        if err != nil {
                fmt.Println("parse error", err.Error())
        }
        fmt.Println(t.Format(time.ANSIC))
}

Playground: http://play.golang.org/p/hvqBgtesLd

See the source code at http://golang.org/src/pkg/time/format.go?s=15404:15450#L607

answered Dec 30, 2012 at 20:23

topskip

17.7k15 gold badges69 silver badges106 bronze badges

Comments

Sonia · Accepted Answer · 2013-01-01 14:07:48Z

5

The documentation for time.String gives the format it uses: "2006-01-02 15:04:05.999999999 -0700 MST". A start would be to use the same format for parsing.

Time zones may be a problem for you though. If you must parse times that you know were produced with time.String, but were produced in other time zones, you must have the zoneinfo for the other time zones. See the documentation under LoadLocation. If you cannot obtain the zoneinfo, cannot install it on your system, or cannot risk failing on some new unknown time zone, then the time.String format is not for you. You will have to obtain time stamps in a different format, or remove the time zone from the strings and parse the modified strings with a modified format.

answered Jan 1, 2013 at 14:07

Sonia

28.6k8 gold badges54 silver badges54 bronze badges

1 Comment

Sonia Over a year ago

Turns out there is a bug in 1.0.3 that is now fixed at tip that kept the .999 format from working. Your problem with FLEST is separate. I recommend that you remove the time zone from the end of the string as I mentioned. Probably I would handle the error by searching for the zone name "FLEST" in the error message and if found, then reparse with the zone name removed from both the string and the format.

Collectives™ on Stack Overflow

Parse Go time stamp using Go

3 Answers 3

1 Comment

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related