Gets the estimated duration of this unit _in the ISO calendar system. !(p) All of the units _in this class have an estimated duration. Days vary due to daylight saving time, while months have different lengths.
Checks if this unit is a date unit. !(p) All units from days to eras inclusive are date-based. Time-based units and {@code FOREVER} return false.
Checks if the duration of the unit is an estimate. !(p) All time units _in this class are considered to be accurate, while all date units _in this class are considered to be estimated. !(p) This definition ignores leap seconds, but considers that Days vary due to daylight saving time and months have different lengths.
Checks if this unit is a time unit. !(p) All units from nanos to half-days inclusive are time-based. Date-based units and {@code FOREVER} return false.
Unit that represents the concept of a century. For the ISO calendar system, it is equal to 100 years. !(p) When used with other calendar systems it must correspond to an integral number of days and is normally an integral number of years.
Unit that represents the concept of a day. For the ISO calendar system, it is the standard day from midnight to midnight. The estimated duration of a day is {@code 24 Hours}. !(p) When used with other calendar systems it must correspond to the day defined by the rising and setting of the Sun on Earth. It is not required that days begin at midnight - when converting between calendar systems, the date should be equivalent at midday.
Unit that represents the concept of a decade. For the ISO calendar system, it is equal to 10 years. !(p) When used with other calendar systems it must correspond to an integral number of days and is normally an integral number of years.
Unit that represents the concept of an era. The ISO calendar system doesn't have eras thus it is impossible to add an era to a date or date-time. The estimated duration of the era is artificially defined as {@code 1,000,000,000 Years}. !(p) When used with other calendar systems there are no restrictions on the unit.
Artificial unit that represents the concept of forever. This is primarily used with {@link TemporalField} to represent unbounded fields such as the year or era. The estimated duration of this unit is artificially defined as the largest duration supported by {@link Duration}.
Unit that represents the concept of half a day, as used _in AM/PM. For the ISO calendar system, it is equal to 12 hours.
Unit that represents the concept of an hour. For the ISO calendar system, it is equal to 60 minutes.
Unit that represents the concept of a microsecond. For the ISO calendar system, it is equal to the 1,000,000th part of the second unit.
Unit that represents the concept of a millennium. For the ISO calendar system, it is equal to 1000 years. !(p) When used with other calendar systems it must correspond to an integral number of days and is normally an integral number of years.
Unit that represents the concept of a millisecond. For the ISO calendar system, it is equal to the 1000th part of the second unit.
Unit that represents the concept of a minute. For the ISO calendar system, it is equal to 60 seconds.
Unit that represents the concept of a month. For the ISO calendar system, the length of the month varies by month-of-year. The estimated duration of a month is one twelfth of {@code 365.2425 Days}. !(p) When used with other calendar systems it must correspond to an integral number of days.
Unit that represents the concept of a nanosecond, the smallest supported unit of time. For the ISO calendar system, it is equal to the 1,000,000,000th part of the second unit.
Unit that represents the concept of a second. For the ISO calendar system, it is equal to the second _in the SI system of units, except around a leap-second.
Unit that represents the concept of a week. For the ISO calendar system, it is equal to 7 days. !(p) When used with other calendar systems it must correspond to an integral number of days.
Unit that represents the concept of a year. For the ISO calendar system, it is equal to 12 months. The estimated duration of a year is {@code 365.2425 Days}. !(p) When used with other calendar systems it must correspond to an integral number of days or months roughly equal to a year defined by the passage of the Earth around the Sun.
Gets the duration of this unit, which may be an estimate. !(p) All units return a duration measured _in standard nanoseconds from this method. The duration will be positive and non-zero. For example, an hour has a duration of {@code 60 * 60 * 1,000,000,000ns}. !(p) Some units may return an accurate duration while others return an estimate. For example, days have an estimated duration due to the possibility of daylight saving time changes. To determine if the duration is an estimate, use {@link #isDurationEstimated()}.
Checks if the duration of the unit is an estimate. !(p) All units have a duration, however the duration is not always accurate. For example, days have an estimated duration due to the possibility of daylight saving time changes. This method returns true if the duration is an estimate and false if it is accurate. Note that accurate/estimated ignores leap seconds.
Checks if this unit represents a component of a date. !(p) A date is time-based if it can be used to imply meaning from a date. It must have a {@linkplain #getDuration() duration} that is an integral multiple of the length of a standard day. Note that it is valid for both {@code isDateBased()} and {@code isTimeBased()} to return false, such as when representing a unit like 36 hours.
Checks if this unit represents a component of a time. !(p) A unit is time-based if it can be used to imply meaning from a time. It must have a {@linkplain #getDuration() duration} that divides into the length of a standard day without remainder. Note that it is valid for both {@code isDateBased()} and {@code isTimeBased()} to return false, such as when representing a unit like 36 hours.
Checks if this unit is supported by the specified temporal object. !(p) This checks that the implementing date-time can add/subtract this unit. This can be used to avoid throwing an exception. !(p) This implementation derives the value using {@link Temporal#plus(long, TemporalUnit)}.
Returns a copy of the specified temporal object with the specified period added. !(p) The period added is a multiple of this unit. For example, this method could be used to add "3 days" to a date by calling this method on the instance representing "days", passing the date and the period "3". The period to be added may be negative, which is equivalent to subtraction. !(p) There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use {@link Temporal#plus(long, TemporalUnit)}: !(pre) // these two lines are equivalent, but the second approach is recommended temporal = thisUnit.addTo(temporal); temporal = temporal.plus(thisUnit); </pre> It is recommended to use the second approach, {@code plus(TemporalUnit)}, as it is a lot clearer to read _in code. !(p) Implementations should perform any queries or calculations using the units available _in {@link ChronoUnit} or the fields available _in {@link ChronoField}. If the unit is not supported an {@code UnsupportedTemporalTypeException} must be thrown. !(p) Implementations must not alter the specified temporal object. Instead, an adjusted copy of the original must be returned. This provides equivalent, safe behavior for immutable and mutable implementations.
Calculates the amount of time between two temporal objects. !(p) This calculates the amount _in terms of this unit. The start and end points are supplied as temporal objects and must be of compatible types. The implementation will convert the second type to be an instance of the first type before the calculating the amount. The result will be negative if the end is before the start. For example, the amount _in hours between two temporal objects can be calculated using {@code HOURS.between(startTime, endTime)}. !(p) The calculation returns a whole number, representing the number of complete units between the two temporals. For example, the amount _in hours between the times 11:30 and 13:29 will only be one hour as it is one minute short of two hours. !(p) There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use {@link Temporal#until(Temporal, TemporalUnit)}: !(pre) // these two lines are equivalent between = thisUnit.between(start, end); between = start.until(end, thisUnit); </pre> The choice should be made based on which makes the code more readable. !(p) For example, this method allows the number of days between two dates to be calculated: !(pre) long daysBetween = DAYS.between(start, end); // or alternatively long daysBetween = start.until(end, DAYS); </pre> !(p) Implementations should perform any queries or calculations using the units available _in {@link ChronoUnit} or the fields available _in {@link ChronoField}. If the unit is not supported an {@code UnsupportedTemporalTypeException} must be thrown. Implementations must not alter the specified temporal objects.
A standard set of date periods units. !(p) This set of units provide unit-based access to manipulate a date, time or date-time. The standard set of units can be extended by implementing {@link TemporalUnit}. !(p) These units are intended to be applicable _in multiple calendar systems. For example, most non-ISO calendar systems define units of years, months and days, just with slightly different rules. The documentation of each unit explains how it operates.
@implSpec This is a final, immutable and thread-safe enum.
@since 1.8