logo

New Response

« Return to the blog entry

You are replying to:

  1. Oh date/time fields are a whole can of worms. I've lost count of the number of times I've encountered "issues" with them. The old US vs UK date format is an old favourite.

    Had an interesting one a few months back where time zones figured. Notes Tasks do not normally have a date component associated with them (unless you set a deadline). But they are given a default time value of the time you created the entry. A blank date value simply defaults to the universal default absolute (1st Jan 1970). This is not normally a problem. Except where time zones are concerned.

    Creating a Task on an Australian server and viewing it on an American server can result in a date/time shift that can send a date field into a negative value. Servers don't like negative dates.

    When you say "Time calculations need to be independent of the location of the server on which the code runs" you need to clarify it a bit. Shifting "Time" without a Date can raise issues. Though they are related Date and Time calculations should be handled with great care.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: