Added in API level 26

TemporalUnit

interface TemporalUnit

java.time.temporal.TemporalUnit

Known Direct Subclasses

ChronoUnit

A standard set of date periods units.

Known Indirect Subclasses

ChronoUnit.CENTURIES, ChronoUnit.DAYS, ChronoUnit.DECADES, ChronoUnit.ERAS, ChronoUnit.FOREVER, ChronoUnit.HALF_DAYS, ChronoUnit.HOURS, ChronoUnit.MICROS, ChronoUnit.MILLENNIA, ChronoUnit.MILLIS, ChronoUnit.MINUTES, ChronoUnit.MONTHS, and 4 others.

ChronoUnit.CENTURIES	Unit that represents the concept of a century.
ChronoUnit.DAYS	Unit that represents the concept of a day.
ChronoUnit.DECADES	Unit that represents the concept of a decade.
ChronoUnit.ERAS	Unit that represents the concept of an era.
ChronoUnit.FOREVER	Artificial unit that represents the concept of forever.
ChronoUnit.HALF_DAYS	Unit that represents the concept of half a day, as used in AM/PM.
ChronoUnit.HOURS	Unit that represents the concept of an hour.
ChronoUnit.MICROS	Unit that represents the concept of a microsecond.
ChronoUnit.MILLENNIA	Unit that represents the concept of a millennium.
ChronoUnit.MILLIS	Unit that represents the concept of a millisecond.
ChronoUnit.MINUTES	Unit that represents the concept of a minute.
ChronoUnit.MONTHS	Unit that represents the concept of a month.
ChronoUnit.NANOS	Unit that represents the concept of a nanosecond, the smallest supported unit of time.
ChronoUnit.SECONDS	Unit that represents the concept of a second.
ChronoUnit.WEEKS	Unit that represents the concept of a week.
ChronoUnit.YEARS	Unit that represents the concept of a year.

A unit of date-time, such as Days or Hours.

Measurement of time is built on units, such as years, months, days, hours, minutes and seconds. Implementations of this interface represent those units.

An instance of this interface represents the unit itself, rather than an amount of the unit. See Period for a class that represents an amount in terms of the common units.

The most commonly used units are defined in ChronoUnit. Further units are supplied in IsoFields. Units can also be written by application code by implementing this interface.

The unit works using double dispatch. Client code calls methods on a date-time like LocalDateTime which check if the unit is a ChronoUnit. If it is, then the date-time must handle it. Otherwise, the method call is re-dispatched to the matching method in this interface.

Summary

Public methods
abstract R	`addTo(temporal: R, amount: Long)` Returns a copy of the specified temporal object with the specified period added.
abstract Long	`between(temporal1Inclusive: Temporal!, temporal2Exclusive: Temporal!)` Calculates the amount of time between two temporal objects.
abstract Duration!	`getDuration()` Gets the duration of this unit, which may be an estimate.
abstract Boolean	`isDateBased()` Checks if this unit represents a component of a date.
abstract Boolean	`isDurationEstimated()` Checks if the duration of the unit is an estimate.
open Boolean	`isSupportedBy(temporal: Temporal!)` Checks if this unit is supported by the specified temporal object.
abstract Boolean	`isTimeBased()` Checks if this unit represents a component of a time.

Public methods

addTo

Added in API level 26

abstract fun <R : Temporal!> addTo(
    temporal: R, 
    amount: Long
): R

Returns a copy of the specified temporal object with the specified period added.

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.

There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use Temporal#plus(long, TemporalUnit):

// these two lines are equivalent, but the second approach is recommended
    temporal = thisUnit.addTo(temporal);
    temporal = temporal.plus(thisUnit);

It is recommended to use the second approach, plus(TemporalUnit), as it is a lot clearer to read in code.

Implementations should perform any queries or calculations using the units available in ChronoUnit or the fields available in ChronoField. If the unit is not supported an UnsupportedTemporalTypeException must be thrown.

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.

Parameters
`<R>`	the type of the Temporal object
`temporal`	R: the temporal object to adjust, not null
`amount`	Long: the amount of this unit to add, positive or negative

Return
`R`	the adjusted temporal object, not null

Exceptions
`java.time.DateTimeException`	if the amount cannot be added
`java.time.temporal.UnsupportedTemporalTypeException`	if the unit is not supported by the temporal

between

Added in API level 26

abstract fun between(
    temporal1Inclusive: Temporal!, 
    temporal2Exclusive: Temporal!
): Long

Calculates the amount of time between two temporal objects.

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 HOURS.between(startTime, endTime).

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.

There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use Temporal#until(Temporal, TemporalUnit):

// these two lines are equivalent
    between = thisUnit.between(start, end);
    between = start.until(end, thisUnit);

The choice should be made based on which makes the code more readable.

For example, this method allows the number of days between two dates to be calculated:

long daysBetween = DAYS.between(start, end);
   // or alternatively
   long daysBetween = start.until(end, DAYS);

Parameters
`temporal1Inclusive`	Temporal!: the base temporal object, not null
`temporal2Exclusive`	Temporal!: the other temporal object, exclusive, not null

Return
`Long`	the amount of time between temporal1Inclusive and temporal2Exclusive in terms of this unit; positive if temporal2Exclusive is later than temporal1Inclusive, negative if earlier

Exceptions
`java.time.DateTimeException`	if the amount cannot be calculated, or the end temporal cannot be converted to the same type as the start temporal
`java.time.temporal.UnsupportedTemporalTypeException`	if the unit is not supported by the temporal
`java.lang.ArithmeticException`	if numeric overflow occurs

getDuration

Added in API level 26

abstract fun getDuration(): Duration!

Gets the duration of this unit, which may be an estimate.

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 60 * 60 * 1,000,000,000ns.

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 isDurationEstimated().

Return
`Duration!`	the duration of this unit, which may be an estimate, not null

isDateBased

Added in API level 26

abstract fun isDateBased(): Boolean

Checks if this unit represents a component of a date.

A date is time-based if it can be used to imply meaning from a date. It must have a duration that is an integral multiple of the length of a standard day. Note that it is valid for both isDateBased() and isTimeBased() to return false, such as when representing a unit like 36 hours.

Return
`Boolean`	true if this unit is a component of a date

isDurationEstimated

Added in API level 26

abstract fun isDurationEstimated(): Boolean

Checks if the duration of the unit is an estimate.

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.

Return
`Boolean`	true if the duration is estimated, false if accurate

isSupportedBy

Added in API level 26

open fun isSupportedBy(temporal: Temporal!): Boolean

Checks if this unit is supported by the specified temporal object.

This checks that the implementing date-time can add/subtract this unit. This can be used to avoid throwing an exception.

This default implementation derives the value using Temporal#plus(long, TemporalUnit).

Parameters
`temporal`	Temporal!: the temporal object to check, not null

Return
`Boolean`	true if the unit is supported

isTimeBased

Added in API level 26

abstract fun isTimeBased(): Boolean

Checks if this unit represents a component of a time.

A unit is time-based if it can be used to imply meaning from a time. It must have a duration that divides into the length of a standard day without remainder. Note that it is valid for both isDateBased() and isTimeBased() to return false, such as when representing a unit like 36 hours.

Return
`Boolean`	true if this unit is a component of a time