the Sweet Smell of Burning Fur (plonq) wrote,
the Sweet Smell of Burning Fur

  • Location:
  • Mood:
  • Music:

Hey guys, can we just agree on ISO8601 and move on?

It's another day, and another report that won't yield output for me. After a fair bit of digging, I discovered that its designer could not settle on a single date format. At one point, he or she formatted the data as "d/M/yy", and then in another variable it was "MM/d/yy". Cringe-worthy two-digit year aside, this probably would have been OK if they had not done some data comparisons between the two in their filters. The result for me was blank tables when I refreshed their job against the server.

I spent a few minutes converting all of their dates to ISO8106, and suddenly the report started working.

I can understand if one converts the format for the report output, since some of our executives are morons, and cannot understand a date if it does not match their desktop flip calendar, but I don't understand why they would convert them for internal calculations. Our servers store the dates in ISO8601. Well, most of our servers do; SAP does it differently in places because many of their designers ate lead paint chips as children.

In short, please don't mess with the dates that come out of Oracle, folks. They set them up that way for a reason.
Tags: iso8601
  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.