unix-timestamp

I'm trying to parse an Unix timestamp but I get out of range error. That doesn't really makes sense to me, because the layout is correct (as in the Go docs): package main import "fmt" import "time" func main() { tm, err := time.Parse("1136239445", "1405544146") if err != nil{ panic(err) } fmt.Println(tm) } Playground The time.Parse function does not do Unix timestamps. Instead you can use strconv.ParseInt to parse the string to int64 and create the timestamp with time.Unix : package main import ( "fmt" "time" "strconv" ) func main() { i, err := strconv.ParseInt("1405544146", 10, 64) if err !=

Is there a quick, one-liner way to convert a Unix timestamp to a date from the Unix command line? date might work, except it's rather awkward to specify each element (month, day, year, hour, etc.), and I can't figure out how to get it to work properly. It seems like there might be an easier way - am I missing something? John Kugelman With GNU's date you can do: date -d "@$TIMESTAMP" # date -d @0 Wed Dec 31 19:00:00 EST 1969 (From: BASH: Convert Unix Timestamp to a Date ) On OS X, use date -r . date -r "$TIMESTAMP" Alternatively, use strftime() . It's not available directly from the shell, but

I am using PHP and jQuery to build an interactive timeline which needs to display dates between 1500 and 2020. I usually use PHP's strtotime function when working with dates, but it does not work for dates pre-1900. The dates will come from a MySQL database, and are formatted as strings such as " January 31, 1654 " (this may not be the ideal format, but I can't change how they are stored). I am using PHP to parse the dates, basically converting them into pixel values which determine where they are displayed on the timeline. What is the easiest way to parse these historical dates? Pascal MARTIN

I've got some JSON that has timestamps in seconds (i.e. a Unix timestamp): {"foo":"bar","timestamp":1386280997} Asking Jackson to deserialize this into an object with a DateTime field for the timestamp results in 1970-01-17T01:11:25.983Z , a time shortly after the epoch because Jackson is assuming it to be in milliseconds . Aside from ripping apart the JSON and adding some zeros, how might I get Jackson to understand the seconds timestamp? I wrote a custom deserializer to handle timestamps in seconds (Groovy syntax). class UnixTimestampDeserializer extends JsonDeserializer<DateTime> { Logger

I know, "no user-serviceable parts inside" ... but I'm curious: In a Core Data sqlite3 DB, it seems I can get at the date within a ZDATE like so: sqlite> select datetime(ZDATE,'unixepoch','31 years','localtime') from ZMYCLASS; 2003-12-11 19:00:00 2009-12-31 19:00:00 2009-01-24 19:00:00 2011-01-01 19:00:00 2009-10-03 20:00:00 ... Unix Epoch I get, but why 31 years? Core Data stores dates relative to reference date, which is Jan 1st, 2001 (31 years after EPOCH as pointed out in the comments) Here's some code to decode the dates from the table, in case it is useful to you. NSNumber *time =