9

We have a library used for generating reports. It reads from a data file (SQL, XML, JSON, etc.), the datetime may then be modified in a user written equation, and then it is formatted as specified for the report output.

The use in an equation can be add a timespan, get parts of the value as in "if date.month == 2", and pretty much all the datetime macros in Excel.

Because the data can be JSON (or XML with no schema) the datetime can be "2019-01-25", "2019-01-25T14:32:23", "2019-01-25T14:32:23.12345", "2019-01-25T14:32:23Z", or "2019-01-25T14:32:23Z-0500" (last two can have the ".12345" also).

If there's no timezone offset we assume the datetime is UTC. While that should be true, often it isn't and it's local time but the way it's used, it doesn't matter. So making it UTC unless a timezone offset is specified works (up till now we've used Date).

First question - what class should I use to hold this value? From what I've read I think ZonedDateTime, but maybe Instant?

Second question - what class should I use for timespan when I have to do something like add 3 days to the datetime?

Third question - is there some parser that can parse all the different strings as I listed above? Or do I need to call String.contains() to determine the format and then do an explicit pattern based on that? And if so, using what class?

Improve this question
9
  • 1
    There are no timezones in your examples, only timezone offsets, so OffsetDateTime would make more sense than ZonedDateTime. Commented Jan 25, 2019 at 14:51
  • Have you considered Joda Time? It is my favourite class for working with time. If you could implement it, I could make an answer about it if you want. Commented Jan 25, 2019 at 14:55
  • @S.Czop we're on Java 1.8 so we're going to use java.time. Commented Jan 25, 2019 at 15:00
  • 2
    @S.Czop why use an external library for something that's now covered in the standard runtime (unless you have to use Java 7). Commented Jan 25, 2019 at 15:00
  • Re. your first Q. looking at your last example 2019-01-25T14:32:23Z-0500: do you need to know the offset of 5hrs? Or are you ok with only keeping the same instant in UTC, i.e. 2019-01-25T19:32:23Z? Or would you prefer having 2019-01-25T14:32:23Z (which is NOT the same instant but the same local time)? Commented Jan 25, 2019 at 15:37

2 Answers 2

Reset to default
6

Third question - is there some parser that can parse all the different strings as I listed above? Or do I need to call String.contains() to determine the format and then do an explicit pattern based on that? And if so, using what class?

I might be horrible wrong, but can you use DateTimeFormatter with optional parts on pattern and parseBest method:

List<String> dates = List.of(
    "2019-01-25", 
    "2019-01-25T14:32:23",
    "2019-01-25T14:32:23.12345", 
    "2019-01-25T14:32:23Z", 
    "2019-01-25T14:32:23Z-0500"
);

DateTimeFormatter formatter = DateTimeFormatter.ofPattern(
   "yyyy-MM-dd['T'[HH:mm:ss][.SSSSS]][z][x]"
); // all the possible combinations

dates.forEach( date -> {
            TemporalAccessor accessor = formatter.parseBest(date,                       
       OffsetDateTime::from, // going from most specific date
       LocalDateTime::from, 
       LocalDate::from); // to the less specific 

            System.out.println( accessor.getClass() + " " + accessor);
        }

);

// output for this is 
class java.time.LocalDate 2019-01-25
class java.time.LocalDateTime 2019-01-25T14:32:23
class java.time.LocalDateTime 2019-01-25T14:32:23.123450
class java.time.OffsetDateTime 2019-01-25T14:32:23Z
class java.time.OffsetDateTime 2019-01-25T14:32:23-05:00
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

3

As to the 2nd question: Yes there is a "timespan" class in the Java JDK.

For a span-of-time not attached to the timeline:

Period

Represents a number of days/weeks/months/years. Can be used in date calculations, automatically accounting for Daylight Savings Time (DST).

For example, to subtract 3 days from a given date, you could do 

ZonedDateTime threeDaysAgo = Period.ofDays(-3).addTo(ZonedDateTime.now());

Duration

Similar to Period but on the scale of days (as 24-hour chunks, not calendar days), hours, minutes, seconds, and fractional second.

ChronoUnit

If you need to do calculations on a wider scale (like include hours/minutes/secods etc) There is also the ChronoUnit enum:

ZonedDateTime threeHoursAgo = ChronoUnit.HOURS.addTo(ZonedDateTime.now(), -3);
Improve this answer

4 Comments

Yes and know - It's not really a timespan in the sense that it doesn't hold the start and end date - not sure if that's an issue. And also doesn't have hour/minute/second precision.
you meant yes and no. and regardless of the meaning of the term, it is exactly what OP requested - a container for something like "3 days" not range between specific days.
edited answer to include a solution for wider range of time units
For a span-of-time attached to the timeline, see the Interval & LocalDateRange classes in the ThreeTen-Extra library.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.