In case you’re restricted to legacy java.util.Date and java.util.Calendar APIs, you need to take into account that the timestamps are interpreted in milliseconds, not seconds. So you first need to multiply it by 1000 to get the timestamp in milliseconds. long seconds = 1320105600; long millis = seconds * 1000; This way you can feed … Read more
Be careful about leap years in your daysInMonth function. If you want very high performance, you can precompute the pair to get to month+year in one step, and then calculate the day/hour/min/sec. A good solution is the one in the gmtime source code: /* * gmtime – convert the calendar time into broken down time … Read more
You are using an Instant to get that milliseconds representation. Instant are not zone based. Now, the epoch time is based on the “1970-01-01T00:00:00Z” so you should not have the zone in it. If you want to create a ZoneDateTime from the epoch value, you can simply create an Instant at that epoch time and … Read more
Both are fine. And neither is recommended except for a minority of purposes. What do you need milliseconds since the epoch for? In Java, we can have many different ways to get the current timestamp, For current timestamp just use Instant.now(). No need to convert to milliseconds. Many methods from the first years of Java, … Read more
Use MySQL’s UNIX_TIMESTAMP function
First, convert it to a datetime object with second precision (floored, not rounded): >>> from datetime import datetime >>> dt = datetime.fromtimestamp(1360287003083988472 // 1000000000) >>> dt datetime.datetime(2013, 2, 7, 17, 30, 3) Then to make it human-readable, use the strftime() method on the object you get back: >>> s = dt.strftime(‘%Y-%m-%d %H:%M:%S’) >>> s ‘2013-02-07 … Read more
java.time Use the java.time classes built into Java 8 and later. LocalDate now = LocalDate.now(); LocalDate epoch = LocalDate.ofEpochDay(0); System.out.println(“Days: ” + ChronoUnit.DAYS.between(epoch, now)); System.out.println(“Weeks: ” + ChronoUnit.WEEKS.between(epoch, now)); System.out.println(“Months: ” + ChronoUnit.MONTHS.between(epoch, now)); Output Days: 16857 Weeks: 2408 Months: 553
It is a function of both the specific clock the time_point refers to, and the implementation of that clock. The standard specifies three different clocks: system_clock steady_clock high_resolution_clock And the standard does not specify the epoch for any of these clocks. Programmers (you) can also author their own clocks, which may or may not specify … Read more
There are two parts: Convert the time string into a broken-down time. See How to parse ISO formatted date in python? Convert the UTC time to “seconds since the Epoch” (POSIX timestamp). #!/usr/bin/env python from datetime import datetime utc_time = datetime.strptime(“2009-03-08T00:27:31.807Z”, “%Y-%m-%dT%H:%M:%S.%fZ”) epoch_time = (utc_time – datetime(1970, 1, 1)).total_seconds() # -> 1236472051.807 If you are … Read more