Examples of DateTime

ch.agent.t2.time.DateTime
A DateTime is a {@link Time2} with second resolution and the origin at2000-01-01. For times before the origin, {@link TimeIndex#asOffset()} will returnnegative values. The domain label is datetime.
This time corresponds to Unix time, except for the "epoch", 2000-01-01 instead of 1970-01-01. @author Jean-Paul Vetterli
ch.pollet.jzic.datetime.DateTime
@author Christophe Pollet
com.aragost.javahg.DateTime
Represents a timestamp and a timezone offset
com.asakusafw.runtime.value.DateTime
日付時刻に関する軽量クラス。
com.bloomberglp.blpapi.Datetime
com.enernoc.open.oadr2.model.DateTime
Some sanity checking for our JAXB-generated models @author Thom Nichols
com.enernoc.open.oadr2.model.v20b.xcal.DateTime
Some sanity checking for our JAXB-generated models @author Thom Nichols
com.facebook.presto.jdbc.internal.joda.time.DateTime
DateTime is the standard implementation of an unmodifiable datetime class.
DateTime is the most widely used implementation of {@link ReadableInstant}. As with all instants, it represents an exact point on the time-line, but limited to the precision of milliseconds. A DateTime calculates its fields with respect to a {@link DateTimeZone time zone}.
Internally, the class holds two pieces of data. Firstly, it holds the datetime as milliseconds from the Java epoch of 1970-01-01T00:00:00Z. Secondly, it holds a {@link Chronology} which determines how themillisecond instant value is converted into the date time fields. The default Chronology is {@link ISOChronology} which is the agreedinternational standard and compatible with the modern Gregorian calendar.
Each individual field can be queried in two ways:
- getHourOfDay()
- hourOfDay().get()
The second technique also provides access to other useful methods on the field:
- numeric value
- text value
- short text value
- maximum/minimum values
- add/subtract
- set
- rounding
DateTime is thread-safe and immutable, provided that the Chronology is as well. All standard Chronology classes supplied are thread-safe and immutable. @author Stephen Colebourne @author Kandarp Shah @author Brian S O'Neill @since 1.0 @see MutableDateTime
com.google.api.ads.dfp.axis.v201208.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.axis.v201211.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.axis.v201302.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.axis.v201306.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.axis.v201308.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.axis.v201311.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.jaxws.v201208.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201208}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.jaxws.v201211.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201211}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.jaxws.v201302.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201302}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.jaxws.v201306.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201306}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.jaxws.v201308.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201308}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.jaxws.v201311.DateTime
3.org/2001/XMLSchema}anyType"> <sequence> <element name="date" type="{https://www.google.com/apis/ads/publisher/v201311}Date" minOccurs="0"/> <element name="hour" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="minute" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="second" type="{http://www.w3.org/2001/XMLSchema}int" minOccurs="0"/> <element name="timeZoneID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
com.google.api.ads.dfp.v201208.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.v201211.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.v201302.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.v201306.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.v201308.DateTime
Represents a date combined with the time of day.
com.google.api.ads.dfp.v201311.DateTime
Represents a date combined with the time of day.
com.google.api.client.util.DateTime
Immutable representation of a date with an optional time and an optional time zone based on RFC 3339.
Implementation is immutable and therefore thread-safe.
@since 1.0 @author Yaniv Inbar
com.google.gdata.data.DateTime
Represents a date/time, or a date without a time. Optionally includes a time zone.
com.sun.star.util.DateTime

hirondelle.date4j.DateTime

st precision is nanosecond, not millisecond: DateTime dateAndTime = new DateTime("2010-01-19 23:59:59.123456789"); DateTime dateOnly = new DateTime("2010-01-19"); DateTime timeOnly = new DateTime("23:59:59"); DateTime dateOnly = DateTime.forDateOnly(2010,01,19); DateTime timeOnly = DateTime.forTimeOnly(23,59,59,0); DateTime dt = new DateTime("2010-01-15 13:59:15"); boolean leap = dt.isLeapYear(); //false dt.getNumDaysInMonth(); //31 dt.getStartOfMonth(); //2010-01-01, 00:00:00 dt.getEndOfDay(); //2010-01-15, 23:59:59 dt.format("YYYY-MM-DD"); //formats as '2010-01-15' dt.plusDays(30); //30 days after Jan 15 dt.numDaysFrom(someDate); //returns an int dueDate.lt(someDate); //less-than dueDate.lteq(someDate); //less-than-or-equal-to DateTime.now(aTimeZone); DateTime.today(aTimeZone); DateTime fromMilliseconds = DateTime.forInstant(31313121L, aTimeZone); birthday.isInFuture(aTimeZone);

Justification For This Class

The fundamental reasons why this class exists are :

to avoid the embarrassing number of distasteful inadequacies in the JDK's date classes
to oppose the very "mental model" of the JDK's date-time classes with something significantly simpler

There are 2 distinct mental models for date-times, and they don't play well together :

timeline - an instant on the timeline, as a physicist would picture it, representing the number of seconds from some epoch. In this picture, such a date-time can have many, many different representations according to calendar and time zone. That is, the date-time, as seen and understood by the end user, can change according to "who's looking at it". It's important to understand that a timeline instant, before being presented to the user, must always have an associated time zone - even in the case of a date only, with no time.
everyday - a date-time in the Gregorian calendar, such as '2009-05-25 18:25:00', which never changes according to "who's looking at it". Here, the time zone is always both implicit and immutable.

The problem is that java.util. {@link java.util.Date} uses only the timeline style, while most users, most of the time, think in terms of the other mental model - the 'everday' style. In particular, there are a large number of applications which experience problems with time zones, because the timeline model is used instead of the everday model. Such problems are often seen by end users as serious bugs, because telling people the wrong date or time is often a serious issue. These problems make you look stupid.

Date Classes in the JDK are Mediocre

The JDK's classes related to dates are widely regarded as frustrating to work with, for various reasons:

mistakes regarding time zones are very common
month indexes are 0-based, leading to off-by-one errors
difficulty of calculating simple time intervals
java.util.Date is mutable, but 'building block' classes should be immutable
numerous other minor nuisances

Joda Time Has Drawbacks As Well

The Joda Time library is used by some programmers as an alternative to the JDK classes. Joda Time has the following drawbacks :

it limits precision to milliseconds. Database timestamp values almost always have a precision of microseconds or even nanoseconds. This is a serious defect: a library should never truncate your data, for any reason.
it's large, with well over 100 items in its javadoc
in order to stay current, it needs to be manually updated occasionally with fresh time zone data
it has mutable versions of classes
it always coerces March 31 + 1 Month to April 30 (for example), without giving you any choice in the matter
some databases allow invalid date values such as '0000-00-00', but Joda Time doesn't seem to be able to handle them

Dates and Times in General

Civil Timekeeping Is Complex

Civil timekeeping is a byzantine hodge-podge of arcane and arbitrary rules. Consider the following :

months have varying numbers of days
one month (February) has a length which depends on the year
not all years have the same number of days
time zone rules spring forth arbitrarily from the fecund imaginations of legislators
summer hours mean that an hour is 'lost' in the spring, while another hour must repeat itself in the autumn, during the switch back to normal time
summer hour logic varies widely across various jurisdictions
the cutover from the Julian calendar to the Gregorian calendar happened at different times in different places, which causes a varying number of days to be 'lost' during the cutover
occasional insertion of leap seconds are used to ensure synchronization with the rotating Earth (whose speed of rotation is gradually slowing down, in an irregular way)
there is no year 0 (1 BC is followed by 1 AD), except in the reckoning used by astronomers

How Databases Treat Dates

Most databases model dates and times using the Gregorian Calendar in an aggressively simplified form, in which :

the Gregorian calendar is extended back in time as if it was in use previous to its inception (the 'proleptic' Gregorian calendar)
the transition between Julian and Gregorian calendars is entirely ignored
leap seconds are entirely ignored
summer hours are entirely ignored
often, even time zones are ignored, in the sense that the underlying database column doesn't usually explicitly store any time zone information.

The final point requires elaboration. Some may doubt its veracity, since they have seen date-time information "change time zone" when retrieved from a database. But this sort of change is usually applied using logic which is external to the data stored in the particular column.

For example, the following items might be used in the calculation of a time zone difference :

time zone setting for the client (or JDBC driver)
time zone setting for the client's connection to the database server
time zone setting of the database server
time zone setting of the host where the database server resides

(Note as well what's missing from the above list: your own application's logic, and the user's time zone preference.)

When an end user sees such changes to a date-time, all they will say to you is "Why did you change it? That's not what I entered" - and this is a completely valid question. Why did you change it? Because you're using the timeline model instead of the everyday model. Perhaps you're using a inappropriate abstraction for what the user really wants.

The Approach Used By This Class

This class takes the following design approach :

it models time in the "everyday" style, not in the "timeline" style (see above)
its precision matches the highest precision used by databases (nanosecond)
it uses only the proleptic Gregorian Calendar, over the years 1..9999
it ignores all non-linearities: summer-hours, leap seconds, and the cutover from Julian to Gregorian calendars
it ignores time zones. Most date-times are stored in columns whose type does not include time zone information (see note above).
it has (very basic) support for wonky dates, such as the magic value 0000-00-00 used by MySQL
it's immutable
it lets you choose among 4 policies for 'day overflow' conditions during calculations

Even though the above list may appear restrictive, it's very likely true that DateTime can handle the dates and times you're currently storing in your database.

Two Sets Of Operations

This class allows for 2 sets of operations: a few "basic" operations, and many "computational" ones.

Basic operations model the date-time as a simple, dumb String, with absolutely no parsing or substructure. This will always allow your application to reflect exactly what is in a ResultSet, with absolutely no modification for time zone, locale, or for anything else.

This is meant as a back-up, to ensure that your application will always be able to, at the very least, display a date-time exactly as it appears in your ResultSet from the database. This style is particularly useful for handling invalid dates such as 2009-00-00, which can in fact be stored by some databases (MySQL, for example). It can also be used to handle unusual items, such as MySQL's TIME datatype.

The basic operations are represented by {@link #DateTime(String)}, {@link #toString()}, and {@link #getRawDateString()}.

Computational operations allow for calculations and formatting. If a computational operation is performed by this class (for example, if the caller asks for the month), then any underlying date-time String must be parseable by this class into its components - year, month, day, and so on. Computational operations require such parsing, while the basic operations do not. Almost all methods in this class are categorized as computational operations.

Parsing DateTime - Accepted Formats

The {@link #DateTime(String)} constructor accepts a String representation of a date-time.The format of the String can take a number of forms. When retrieving date-times from a database, the majority of cases will have little problem in conforming to these formats. If necessary, your SQL statements can almost always use database formatting functions to generate a String whose format conforms to one of the many formats accepted by the {@link #DateTime(String)} constructor.

The {@link #isParseable(String)} method lets you explicitly test if a given String is in a form that can be parsed by this class.

Mini-Language for Formatting

This class defines a simple mini-language for formatting a DateTime, used by the various format methods.

The following table defines the symbols used by this mini-language, and the corresponding text they would generate given the date:

1958-04-09 Wednesday, 03:05:06.123456789 AM

in an English Locale. (Items related to date are in upper case, and items related to time are in lower case.)

Format	Output	Description	Needs Locale?
YYYY	1958	Year	...
YY	58	Year without century	...
M	4	Month 1..12	...
MM	04	Month 01..12	...
MMM	Apr	Month Jan..Dec	Yes
MMMM	April	Month January..December	Yes
DD	09	Day 01..31	...
D	9	Day 1..31	...
WWWW	Wednesday	Weekday Sunday..Saturday	Yes
WWW	Wed	Weekday Sun..Sat	Yes
hh	03	Hour 01..23	...
h	3	Hour 1..23	...
hh12	03	Hour 01..12	...
h12	3	Hour 1..12	...
a	AM	AM/PM Indicator	Yes
mm	05	Minutes 01..59	...
m	5	Minutes 1..59	...
ss	06	Seconds 01..59	...
s	6	Seconds 1..59	...
f	1	Fractional Seconds, 1 decimal	...
ff	12	Fractional Seconds, 2 decimals	...
fff	123	Fractional Seconds, 3 decimals	...
ffff	1234	Fractional Seconds, 4 decimals	...
fffff	12345	Fractional Seconds, 5 decimals	...
ffffff	123456	Fractional Seconds, 6 decimals	...
fffffff	1234567	Fractional Seconds, 7 decimals	...
ffffffff	12345678	Fractional Seconds, 8 decimals	...
fffffffff	123456789	Fractional Seconds, 9 decimals	...
\|	(no example)	Escape characters	...

As indicated above, some of these symbols can only be used with an accompanying Locale. In general, if the output is text, not a number, then a Locale will be needed. For example, 'September' is localizable text, while '09' is a numeric representation, which doesn't require a Locale. Thus, the symbol 'MM' can be used without a Locale, while 'MMMM' and 'MMM' both require a Locale, since they generate text, not a number.

The fractional seconds 'f' doesn't perform any rounding.

The escape character '|' allows you to insert arbitrary text. The escape character always appears in pairs; these pairs define a range of characters over which the text will not be interpreted using the special format symbols defined above.

Here are some practical examples of using the above formatting symbols:

Format	Output
YYYY-MM-DD hh:mm:ss.fffffffff a	1958-04-09 03:05:06.123456789 AM
YYYY-MM-DD hh:mm:ss.fff a	1958-04-09 03:05:06.123 AM
YYYY-MM-DD	1958-04-09
hh:mm:ss.fffffffff	03:05:06.123456789
hh:mm:ss	03:05:06
YYYY-M-D h:m:s	1958-4-9 3:5:6
WWWW, MMMM D, YYYY	Wednesday, April 9, 1958
WWWW, MMMM D, YYYY \|at\| D a	Wednesday, April 9, 1958 at 3 AM

In the last example, the escape characters are needed only because 'a', the formating symbol for am/pm, appears in the text.

Passing DateTime Objects to the Database

When a DateTime is passed as a parameter to an SQL statement, the DateTime can always be formatted into a String of a form accepted by the database, using one of the format methods.

hirondelle.web4j.model.DateTime

st precision is nanosecond, not millisecond: DateTime dateAndTime = new DateTime("2010-01-19 23:59:59.123456789"); DateTime dateOnly = new DateTime("2010-01-19"); DateTime timeOnly = new DateTime("23:59:59"); DateTime dateOnly = DateTime.forDateOnly(2010,01,19); DateTime timeOnly = DateTime.forTimeOnly(23,59,59,0); DateTime dt = new DateTime("2010-01-15 13:59:15"); boolean leap = dt.isLeapYear(); //false dt.getNumDaysInMonth(); //31 dt.getStartOfMonth(); //2010-01-01, 00:00:00 dt.getEndOfDay(); //2010-01-15, 23:59:59 dt.format("YYYY-MM-DD"); //formats as '2010-01-15' dt.plusDays(30); //30 days after Jan 15 dt.numDaysFrom(someDate); //returns an int dueDate.lt(someDate); //less-than dueDate.lteq(someDate); //less-than-or-equal-to // {@link ActionImpl#getTimeZone()} is readily available in most ActionsDateTime.now(getTimeZone()); DateTime.today(getTimeZone()); DateTime fromMilliseconds = DateTime.forInstant(31313121L, getTimeZone()); birthday.isInFuture(getTimeZone());

Justification For This Class

The fundamental reasons why this class exists are :

to avoid the embarrassing number of distasteful inadequacies in the JDK's date classes
to oppose the very "mental model" of the JDK's date-time classes with something significantly simpler

There are 2 distinct mental models for date-times, and they don't play well together :

timeline - an instant on the timeline, as a physicist would picture it, representing the number of seconds from some epoch. In this picture, such a date-time can have many, many different representations according to calendar and time zone. That is, the date-time, as seen and understood by the end user, can change according to "who's looking at it". It's important to understand that a timeline instant, before being presented to the user, must always have an associated time zone - even in the case of a date only, with no time.
everyday - a date-time in the Gregorian calendar, such as '2009-05-25 18:25:00', which never changes according to "who's looking at it". Here, the time zone is always both implicit and immutable.

Date Classes in the JDK are Mediocre

The JDK's classes related to dates are widely regarded as frustrating to work with, for various reasons:

mistakes regarding time zones are very common
month indexes are 0-based, leading to off-by-one errors
difficulty of calculating simple time intervals
java.util.Date is mutable, but 'building block' classes should be immutable
numerous other minor nuisances

Joda Time Has Drawbacks As Well

The Joda Time library is used by some programmers as an alternative to the JDK classes. Joda Time has the following drawbacks :

it limits precision to milliseconds. Database timestamp values almost always have a precision of microseconds or even nanoseconds. This is a serious defect: a library should never truncate your data, for any reason.
it's large, with well over 100 items in its javadoc
in order to stay current, it needs to be manually updated occasionally with fresh time zone data
it has mutable versions of classes
it always coerces March 31 + 1 Month to April 30 (for example), without giving you any choice in the matter
some databases allow invalid date values such as '0000-00-00', but Joda Time doesn't seem to be able to handle them

Dates and Times in General

Civil Timekeeping Is Complex

Civil timekeeping is a byzantine hodge-podge of arcane and arbitrary rules. Consider the following :

months have varying numbers of days
one month (February) has a length which depends on the year
not all years have the same number of days
time zone rules spring forth arbitrarily from the fecund imaginations of legislators
summer hours mean that an hour is 'lost' in the spring, while another hour must repeat itself in the autumn, during the switch back to normal time
summer hour logic varies widely across various jurisdictions
the cutover from the Julian calendar to the Gregorian calendar happened at different times in different places, which causes a varying number of days to be 'lost' during the cutover
occasional insertion of leap seconds are used to ensure synchronization with the rotating Earth (whose speed of rotation is gradually slowing down, in an irregular way)
there is no year 0 (1 BC is followed by 1 AD), except in the reckoning used by astronomers

How Databases Treat Dates

Most databases model dates and times using the Gregorian Calendar in an aggressively simplified form, in which :

the Gregorian calendar is extended back in time as if it was in use previous to its inception (the 'proleptic' Gregorian calendar)
the transition between Julian and Gregorian calendars is entirely ignored
leap seconds are entirely ignored
summer hours are entirely ignored
often, even time zones are ignored, in the sense that the underlying database column doesn't usually explicitly store any time zone information.

For example, the following items might be used in the calculation of a time zone difference :

time zone setting for the client (or JDBC driver)
time zone setting for the client's connection to the database server
time zone setting of the database server
time zone setting of the host where the database server resides

(Note as well what's missing from the above list: your own application's logic, and the user's time zone preference.)

The Approach Used By This Class

This class takes the following design approach :

it models time in the "everyday" style, not in the "timeline" style (see above)
its precision matches the highest precision used by databases (nanosecond)
it uses only the proleptic Gregorian Calendar, over the years 1..9999
it ignores all non-linearities: summer-hours, leap seconds, and the cutover from Julian to Gregorian calendars
it ignores time zones. Most date-times are stored in columns whose type does not include time zone information (see note above).
it has (very basic) support for wonky dates, such as the magic value 0000-00-00 used by MySQL
it's immutable
it lets you choose among 4 policies for 'day overflow' conditions during calculations
it talks to your {@link TimeSource} implementation when returning the current moment, allowing you to customise dates during testing

Even though the above list may appear restrictive, it's very likely true that DateTime can handle the dates and times you're currently storing in your database.

Two Sets Of Operations

This class allows for 2 sets of operations: a few "basic" operations, and many "computational" ones.

The basic operations are represented by {@link #DateTime(String)}, {@link #toString()}, and {@link #getRawDateString()}.

Parsing DateTime - Accepted Formats

Mini-Language for Formatting

This class defines a simple mini-language for formatting a DateTime, used by the various format methods.

The following table defines the symbols used by this mini-language, and the corresponding text they would generate given the date:

1958-04-09 Wednesday, 03:05:06.123456789 AM

in an English Locale. (Items related to date are in upper case, and items related to time are in lower case.)

Format	Output	Description	Needs Locale?
YYYY	1958	Year	...
YY	58	Year without century	...
M	4	Month 1..12	...
MM	04	Month 01..12	...
MMM	Apr	Month Jan..Dec	Yes
MMMM	April	Month January..December	Yes
DD	09	Day 01..31	...
D	9	Day 1..31	...
WWWW	Wednesday	Weekday Sunday..Saturday	Yes
WWW	Wed	Weekday Sun..Sat	Yes
hh	03	Hour 01..23	...
h	3	Hour 1..23	...
hh12	03	Hour 01..12	...
h12	3	Hour 1..12	...
a	AM	AM/PM Indicator	Yes
mm	05	Minutes 01..59	...
m	5	Minutes 1..59	...
ss	06	Seconds 01..59	...
s	6	Seconds 1..59	...
f	1	Fractional Seconds, 1 decimal	...
ff	12	Fractional Seconds, 2 decimals	...
fff	123	Fractional Seconds, 3 decimals	...
ffff	1234	Fractional Seconds, 4 decimals	...
fffff	12345	Fractional Seconds, 5 decimals	...
ffffff	123456	Fractional Seconds, 6 decimals	...
fffffff	1234567	Fractional Seconds, 7 decimals	...
ffffffff	12345678	Fractional Seconds, 8 decimals	...
fffffffff	123456789	Fractional Seconds, 9 decimals	...
\|	(no example)	Escape character	...

The fractional seconds 'f' does not perform any rounding. The escape character '|' allows you to insert arbitrary text.

Examples :

Format	Output
YYYY-MM-DD hh:mm:ss.fffffffff a	1958-04-09 03:05:06.123456789 AM
YYYY-MM-DD hh:mm:ss.fff a	1958-04-09 03:05:06.123 AM
YYYY-MM-DD	1958-04-09
hh:mm:ss.fffffffff	03:05:06.123456789
hh:mm:ss	03:05:06
YYYY-M-D h:m:s	1958-4-9 3:5:6
WWWW, MMMM D, YYYY	Wednesday, April 9, 1958
WWWW, MMMM D, YYYY \|at\| D a	Wednesday, April 9, 1958 at 3 AM

Interaction with {@link TimeSource}

The methods of this class related to the current date interact with your configured implementation of {@link hirondelle.web4j.util.TimeSource}. That is, {@link #now(TimeZone)} and {@link #today(TimeZone)}will return values derived from {@link TimeSource}. Thus, callers of this class automatically use any 'fake' system clock that you may want to define.

Passing DateTime Objects to the Database

When a DateTime is passed as a parameter to an SQL statement, the DateTime is formatted into a String of a form accepted by the database. There are two mechanisms to accomplish this

in your DAO code, format the DateTime explicitly as a String, using one of the format methods, and pass the String as the parameter to the SQL statement, and not the actual DateTime
pass the DateTime itself. In this case, WEB4J will use the setting in web.xml named DateTimeFormatForPassingParamsToDb to perform the formatting for you. If the formats defined by this setting are not appropriate for a given case, you will need to format the DateTime as a String explicitly instead.

in.partake.base.DateTime
jxl.write.DateTime
A Date which may be created on the fly by a user application and added to a spreadsheet NOTE: By default, all dates will have local timezone information added to their UTC value. If this is not desired (eg. if the date entered represents an interval eg. 9.83s for the 100m world record, then use the overloaded constructor which indicate that the date passed in was created under the GMT timezone. It is important that when the date was created, an instruction like Calendar.setTimeZone(TimeZone.getTimeZone("GMT")) was made prior to that
lotus.domino.DateTime
net.fortuna.ical4j.model.DateTime
org.apache.abdera.model.DateTime

An element conforming to the Atom Date Construct. The data type implementation for this element is provided by the AtomDate class.
org.apache.isis.applib.value.DateTime
Value object representing a date and time value. By default, the time is initialised to the current time, unless otherwise specified.
org.apache.james.mime4j.dom.datetime.DateTime
org.apache.james.mime4j.field.datetime.DateTime
org.apache.sqoop.schema.type.DateTime
Date and time information together. JDBC Types: datetime, timestamp
org.eclipse.persistence.jpa.jpql.parser.DateTime
This {@link Expression} represents a date or time. It supports the following identifiers:
CURRENT_DATE: This function returns the value of current date on the database server.
CURRENT_TIME: This function returns the value of current time on the database server.
CURRENT_TIMESTAMP: This function returns the value of current timestamp on the database server.

BNF: functions_returning_datetime ::= CURRENT_DATE | CURRENT_TIME | CURRENT_TIMESTAMP
The JDBC escape syntax may be used for the specification of date, time, and timestamp literals.

BNF: expression ::= {d 'yyyy-mm-dd'} | {t 'hh:mm:ss'} | {ts 'yyyy-mm-dd hh:mm:ss.f...'}
@version 2.4 @since 2.3 @author Pascal Filion
org.eclipse.swt.widgets.DateTime
ipse.org/swt/snippets/#datetime">DateTime snippets @see SWT Example: ControlExample @see Sample code and further information @since 3.3 @noextend This class is not intended to be subclassed by clients.
org.elasticsearch.common.joda.time.DateTime
org.exolab.castor.types.DateTime
Describe an XML schema DateTime.
The format is defined by W3C XML Schema Recommendation and ISO8601 i.e (-)CCYY-MM-DD'T'HH:MM:SS(.SSSSS)(Z|(+|-)hh:mm) @author Edward Kuns @version $Revision: 0000 $
org.goda.time.DateTime
DateTime is the standard implementation of an unmodifiable datetime class.
DateTime is the most widely used implementation of {@link ReadableInstant}. As with all instants, it represents an exact point on the time-line, but limited to the precision of milliseconds. A DateTime calculates its fields with respect to a {@link DateTimeZone time zone}.
Internally, the class holds two pieces of data. Firstly, it holds the datetime as milliseconds from the Java epoch of 1970-01-01T00:00:00Z. Secondly, it holds a {@link Chronology} which determines how themillisecond instant value is converted into the date time fields. The default Chronology is {@link ISOChronology} which is the agreedinternational standard and compatible with the modern Gregorian calendar.
Each individual field can be queried in two ways:
- getHourOfDay()
- hourOfDay().get()
The second technique also provides access to other useful methods on the field:
- numeric value
- text value
- short text value
- maximum/minimum values
- add/subtract
- set
- rounding
DateTime is thread-safe and immutable, provided that the Chronology is as well. All standard Chronology classes supplied are thread-safe and immutable. @author Stephen Colebourne @author Kandarp Shah @author Brian S O'Neill @since 1.0 @see MutableDateTime
org.jboss.dna.graph.properties.DateTime
org.jboss.dna.graph.property.DateTime
rg/en/jsr/detail?id=310">JSR-310, which will be based upon Joda-Time. This class serves as a stable migration path toward the new JSR 310 classes.
org.joda.time.DateTime
DateTime is the standard implementation of an unmodifiable datetime class.
DateTime is the most widely used implementation of {@link ReadableInstant}. As with all instants, it represents an exact point on the time-line, but limited to the precision of milliseconds. A DateTime calculates its fields with respect to a {@link DateTimeZone time zone}.
Internally, the class holds two pieces of data. Firstly, it holds the datetime as milliseconds from the Java epoch of 1970-01-01T00:00:00Z. Secondly, it holds a {@link Chronology} which determines how themillisecond instant value is converted into the date time fields. The default Chronology is {@link ISOChronology} which is the agreedinternational standard and compatible with the modern Gregorian calendar.
Each individual field can be queried in two ways:
- getHourOfDay()
- hourOfDay().get()
The second technique also provides access to other useful methods on the field:
- numeric value
- text value
- short text value
- maximum/minimum values
- add/subtract
- set
- rounding
DateTime is thread-safe and immutable, provided that the Chronology is as well. All standard Chronology classes supplied are thread-safe and immutable. @author Stephen Colebourne @author Kandarp Shah @author Brian S O'Neill @since 1.0 @see MutableDateTime
org.modeshape.jcr.api.value.DateTime
rg/en/jsr/detail?id=310">JSR-310, which will be based upon Joda-Time. This class serves as a stable migration path toward the new JSR 310 classes. @since 3.0
org.mule.el.datetime.DateTime
Models a DateTime and simplifies the parsing/formatting and very basic manipulation of dates via Mule expression language.
org.openntf.domino.DateTime
The Interface DateTime.
org.openntf.domino.impl.DateTime
The Class DateTime.
org.openntf.formula.DateTime
This is the DateTime interface that is used in formulas. It is very similar to the org.opennft.domino.DateTime interface but this has no dependency to the lotus API, so that the formula engine can be used in a non-notes environmment.
pt.opensoft.util.DateTime
uma data baseada na hora GMT, mas com time zone nos A�ores DateTime date = new DateTime("2007-01-23 11:00:00", new AtlanticAzoresTimeZone()); // usa o formatter do DateTime para mostrar a hora local nos A�ores (menos 1 hora) System.out.println(date.formatDateTime()); obt�m-se 2007-01-23 10:00:00

Se quisermos mostrar a hora em Lisboa com esta mesma inst�ncia do DateTime temos que usar um formatter com o default time zone:
```
 // formatter para Lisboa (default) DateFormat fmtLx = new SimpleDateFormat(DateTime.DATE_FORMAT); // usa um formatter com timezone de Lisboa para apresentar a hora em Lisboa System.out.println(fmtLx.format(date)); 
```
obt�m-se 2007-01-23 11:00:00

O comportamento do construtor � equivalente a ter um DateTime e fazer posteriormente o {@link #setTimeZone(TimeZone)}.
@see AtlanticAzoresTimeZone
railo.runtime.type.dt.DateTime
visad.DateTime

Examples of ch.agent.t2.time.DateTime

    }


    @Override
    public DateTime scan(String value) throws T2DBException {
      try {
        return new DateTime(value);
      } catch (Exception e) {
        throw T2DBMsg.exception(e, D.D10107, value, ValueType.class.getName());
      }
    }

View Full Code Here

Examples of ch.pollet.jzic.datetime.DateTime

        }
    }


    private TreeSet<Period> computePeriods(TreeSet<Zone> zoneData) throws DateTimeException {
        TreeSet<Period> compiledZone = new TreeSet<Period>();
        DateTime from = new DateTime();


        from.setYear(Integer.MIN_VALUE);
        //from.setYear(minYear);
        from.setMonth(1);
        from.setDay(1);
        from.setHour(0);
        from.setMinute(0);
        from.setSecond(0);
        from.setType(DateTime.Type.UTC);


        for (Zone zone : zoneData) {
            Period period = new Period(zone);


            period.setFrom(from);

View Full Code Here

Examples of com.aragost.javahg.DateTime

        boolean negative = match('-');
        int timezoneOffset = 1000 * decimalIntUpTo(stopByte);
        if (negative) {
            timezoneOffset = -timezoneOffset;
        }
        return new DateTime(millis, timezoneOffset);
    }

View Full Code Here

Examples of com.asakusafw.runtime.value.DateTime

            all.set("c_long", 100000L);
            all.set("c_float", 1.5f);
            all.set("c_double", 2.5f);
            all.set("c_decimal", new BigDecimal("3.1415"));
            all.set("c_date", new Date(2011, 9, 1));
            all.set("c_datetime", new DateTime(2011, 12, 31, 23, 59, 59));
            p.setParameters(all.unwrap());
            ps.executeUpdate();


            ps.close();

View Full Code Here

Examples of com.bloomberglp.blpapi.Datetime

      Element fieldDataArray = securityElem.getElement(FIELD_DATA);


      int numValues = fieldDataArray.numValues();
      for (int i = 0; i < numValues; i++) {
        Element fieldData = fieldDataArray.getValueAsElement(i);
        Datetime date = fieldData.getElementAsDate("date");
        LocalDate ldate = LocalDate.of(date.year(), date.month(), date.dayOfMonth());
        double lastPrice = fieldData.getElementAsFloat64(field);
        bld.put(ldate, lastPrice);
      }
    }

View Full Code Here

Examples of com.enernoc.open.oadr2.model.DateTime

                .withModificationNumber(0)
                .withEventStatus(EventStatusEnumeratedType.FAR)
                .withPriority(1L)
                .withEiMarketContext(new EiMarketContext(
                    new MarketContext("http://enernoc.com")))
                .withCreatedDateTime(new DateTime(startDttm)))
            .withEiActivePeriod(new EiActivePeriod()
                .withProperties(new Properties()
                    .withDtstart(new Dtstart(new DateTime(startDttm)))
                    .withDuration(new DurationPropType(new DurationValue("PT1M")))
                    .withTolerance( new Tolerance(new Tolerate(new DurationValue("PT5S"))))
                    .withXEiNotification(new DurationPropType(new DurationValue("PT5S")))
                ))
            .withEiEventSignals( new EiEventSignals()

View Full Code Here

Examples of com.enernoc.open.oadr2.model.v20b.xcal.DateTime

                    .withModificationNumber(0)
                    .withEventStatus(EventStatusEnumeratedType.FAR)
                    .withPriority(1L)
                    .withEiMarketContext(new EiMarketContext(
                        new MarketContext("http://enernoc.com")))
                    .withCreatedDateTime(new DateTime(startDttm)))
                .withEiActivePeriod(new EiActivePeriod()
                    .withProperties(new Properties()
                        .withDtstart(new Dtstart(new DateTime(startDttm)))
                        .withDuration(new DurationPropType(new DurationValue("PT1M")))
                        .withTolerance( new Tolerance(new Tolerate(new DurationValue("PT5S"))))
                        .withXEiNotification(new DurationPropType(new DurationValue("PT5S")))
                    ))
                .withEiEventSignals( new EiEventSignals()
                    .withEiEventSignals( new EiEventSignal()
                        .withSignalID("hi there")
                        .withCurrentValue(new CurrentValue(new PayloadFloatType(1.0f)))
                        .withSignalName("simple")
                        .withSignalType(SignalTypeEnumeratedType.LEVEL)
                        .withIntervals( new Intervals()
                            .withIntervals( new Interval()
                              .withStreamPayloadBases( eiObjectFactory.createSignalPayload(
                                      new SignalPayload( eiObjectFactory.createPayloadFloat( 
                                              new PayloadFloatType( 1.0f) ) ) ) )
                              .withDuration( new DurationPropType( new DurationValue( "PT1M" )) )
                              .withDtstart( new Dtstart(new DateTime( startDttm )) )
                            )
                        )
                    )
                )
            )

View Full Code Here

Examples of com.facebook.presto.jdbc.internal.joda.time.DateTime

    public ReadableDateTime deserialize(JsonParser jp, DeserializationContext ctxt)
        throws IOException, JsonProcessingException
    {
        JsonToken t = jp.getCurrentToken();
        if (t == JsonToken.VALUE_NUMBER_INT) {
            return new DateTime(jp.getLongValue(), DateTimeZone.UTC);
        }
        if (t == JsonToken.VALUE_STRING) {
            String str = jp.getText().trim();
            if (str.length() == 0) { // [JACKSON-360]
                return null;
            }
            return new DateTime(str, DateTimeZone.UTC);
        }
        throw ctxt.mappingException(getValueClass());
    }

View Full Code Here

Examples of com.google.api.ads.dfp.axis.v201208.DateTime

    numberValue2.setValue("1.02");


    numberValue3 = new NumberValue();
    numberValue3.setValue("-1");


    dateTime1 = new DateTime();
    Date date1 = new Date();
    date1.setYear(2012);
    date1.setMonth(12);
    date1.setDay(2);
    dateTime1.setDate(date1);

View Full Code Here

Examples of com.google.api.ads.dfp.axis.v201211.DateTime

    numberValue2.setValue("1.02");


    numberValue3 = new NumberValue();
    numberValue3.setValue("-1");


    dateTime1 = new DateTime();
    Date date1 = new Date();
    date1.setYear(2012);
    date1.setMonth(12);
    date1.setDay(2);
    dateTime1.setDate(date1);

View Full Code Here

0 1 2 3 4 5 6 7 8 9

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.