Examples of ReadablePeriod

com.facebook.presto.jdbc.internal.joda.time.ReadablePeriod
Defines a time period specified in terms of individual duration fields such as years and days.
The implementation of this interface may be mutable or immutable. This interface only gives access to retrieve data, never to change it.
Periods are split up into multiple fields, for example days and seconds. Implementations are not required to evenly distribute the values across the fields. The value for each field may be positive or negative.
When a time period is added to an instant, the effect is to add each field in turn. For example, a time period could be defined as 3 months, 2 days and -1 hours. In most circumstances this would be the same as 3 months, 1 day, and 23 hours. However, when adding across a daylight savings boundary, a day may be 23 or 25 hours long. Thus, the time period is always added field by field to the datetime.
Periods are independent of chronology, and can only be treated as durations when paired with a time via an interval. @see ReadableDuration @see ReadableInterval @author Brian S O'Neill @author Stephen Colebourne @since 1.0
org.goda.time.ReadablePeriod
Defines a time period specified in terms of individual duration fields such as years and days.
The implementation of this interface may be mutable or immutable. This interface only gives access to retrieve data, never to change it.
Periods are split up into multiple fields, for example days and seconds. Implementations are not required to evenly distribute the values across the fields. The value for each field may be positive or negative.
When a time period is added to an instant, the effect is to add each field in turn. For example, a time period could be defined as 3 months, 2 days and -1 hours. In most circumstances this would be the same as 3 months, 1 day, and 23 hours. However, when adding across a daylight savings boundary, a day may be 23 or 25 hours long. Thus, the time period is always added field by field to the datetime.
Periods are independent of chronology, and can only be treated as durations when paired with a time via an interval. @see ReadableDuration @see ReadableInterval @author Brian S O'Neill @author Stephen Colebourne @since 1.0
org.joda.time.ReadablePeriod
Defines a time period specified in terms of individual duration fields such as years and days.
The implementation of this interface may be mutable or immutable. This interface only gives access to retrieve data, never to change it.
Periods are split up into multiple fields, for example days and seconds. Implementations are not required to evenly distribute the values across the fields. The value for each field may be positive or negative.
When a time period is added to an instant, the effect is to add each field in turn. For example, a time period could be defined as 3 months, 2 days and -1 hours. In most circumstances this would be the same as 3 months, 1 day, and 23 hours. However, when adding across a daylight savings boundary, a day may be 23 or 25 hours long. Thus, the time period is always added field by field to the datetime.
Periods are independent of chronology, and can only be treated as durations when paired with a time via an interval. @see ReadableDuration @see ReadableInterval @author Brian S O'Neill @author Stephen Colebourne @since 1.0

Examples of org.joda.time.ReadablePeriod

                      addError(req, "Invalid date: '" + scheduledDate + "'");
                      return "";
                    }
                  }
  
                  ReadablePeriod thePeriod = null;
                  if(hasParam(req, "is_recurring"))
                      thePeriod = parsePeriod(req);
  
                  if(isPm && hour < 12)
                      hour += 12;

View Full Code Here

0 1 2 3

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.