Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-10442

Handling of old dates

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 4.4.0
    • 4.3.0, 4.4.0
    • None
    • None
    • 4.4 M3

      Using dates before a given date (depending on the time-zone) in a content launch errors.

      During writing, a LocalDate value is converted into a Calendar value. If the date is anterior to a specific date, a time offset is applied to the date, adding minutes and seconds

      During reading, the calendar value is checked to verify it is a DateTime, and launch an error for any calendar that have hours, minutes or seconds.

      We should be able to write dates prior to 1900 and still be able to read them without error

        1. image-2020-07-30-12-24-09-082.png
          image-2020-07-30-12-24-09-082.png
          18 kB
        2. image-2020-07-30-09-35-01-689.png
          image-2020-07-30-09-35-01-689.png
          10 kB
        3. image-2020-07-30-09-34-22-324.png
          image-2020-07-30-09-34-22-324.png
          13 kB
        4. image-2020-07-30-09-32-53-985.png
          image-2020-07-30-09-32-53-985.png
          3 kB
        5. image-2020-07-30-09-31-47-811.png
          image-2020-07-30-09-31-47-811.png
          3 kB
        6. image-2020-07-28-17-12-42-376.png
          image-2020-07-28-17-12-42-376.png
          10 kB
        7. image-2020-07-28-17-08-56-592.png
          image-2020-07-28-17-08-56-592.png
          10 kB

          [CMS-10442] Handling of old dates

          Cédric Damioli added a comment -

          From the ISO8601 norm :

          NOTE: Following ISO 8601, numeric offsets represent only time zones that differ from UTC by an integral number of minutes.
      However, many historical time zones differ from UTC by a non-integral number of minutes.  To represent such historical time stamps exactly, applications must convert them to a representable time zone.

          So we should not try to store in JCR invalid ISO-8601 date times.
          Practically, this means that we should treat every LocalDate as 00:00:00 UTC and that we should change every ZonedDateTime's offset to UTC before storage

          Cédric Damioli added a comment - From the ISO8601 norm : NOTE: Following ISO 8601, numeric offsets represent only time zones that differ from UTC by an integral number of minutes. However, many historical time zones differ from UTC by a non-integral number of minutes. To represent such historical time stamps exactly, applications must convert them to a representable time zone. So we should not try to store in JCR invalid ISO-8601 date times. Practically, this means that we should treat every LocalDate as 00:00:00 UTC and that we should change every ZonedDateTime's offset to UTC before storage

          Olivier Gehin added a comment -

          fail with 1909

          Olivier Gehin added a comment - fail with 1909

            cedric Cédric Damioli
            kbourgoin Kepa Bourgoin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: