Improved comment for DateOnly.

[jarosmpost]

No description provided.

[lbovet]

As this comment appears in the generated documentation, I would prefer to keep it short (I find it already too long, btw).
Also, the additional text does not really add information because the example date is already giving the same information.

[jarosmpost]

As this comment appears in the generated documentation, I would prefer to keep it short (I find it already too long, btw). Also, the additional text does not really add information because the example date is already giving the same information.

Since the date has no time zone according to the specification, no exact time can be defined with it. I think this is a very important piece of information.

We should mention this, similar to https://docs.oracle.com/javase/8/docs/api/java/time/LocalDate.html:
'This class does not store or represent a time or time-zone. Instead, it is a description of the date, as used for birthdays. It cannot represent an instant on the time-line without additional information such as an offset or time-zone.'

[lbovet]

Per definition, a date in the format yyyy-mm-dd does not contain hours nor timezone information. I don't see the need to repeat it in prosa.

[jarosmpost]

Per definition, a date in the format yyyy-mm-dd does not contain hours nor timezone information. I don't see the need to repeat it in prosa.

A date is assumed to start at midnight. But when is midnight when you don't know the time zone?

[lbovet]

If you want to refer to a point in time, you use date-time which is millisecond accurate and timezone dependent.
When you refer to a day, you use a yyyy-mm-dd date.

[jarosmpost]

If you want to refer to a point in time, you use date-time which is millisecond accurate and timezone dependent. When you refer to a day, you use a yyyy-mm-dd date.

If I have an entity with a validity from 1.1.2022 to 31.1.2022 in CET, I will always use datatype DateTime. Even if I do not use the time information. With the data type DateOnly, I cannot create a java.sql.Date in Java until I know a time zone.

[lbovet]

If you want to map to a java.util.Date, then you need a timezone information yes. By definition, with a date it is the local timezone.

[jarosmpost]

If you want to map to a java.util.Date, then you need a timezone information yes. By definition, with a date it is the local timezone.

If I run my application in the cloud, then the local time zone is UTC, but on my notebook it is CET. Generally, from a technical point of view, I prefer UTC, but the business partly demands CET. How can I distinguish what applies?