Re: Recording and looking up dates, when day-wide precision is required
Re: Recording and looking up dates, when day-wide precision is required
- Subject: Re: Recording and looking up dates, when day-wide precision is required
- From: Lachlan Deck <email@hidden>
- Date: Tue, 30 Dec 2008 21:03:09 +1100
Hi there,
On 30/12/2008, at 7:47 PM, Andrew Lindesay wrote:
I _think_ (correct me if I'm wrong) Florijan would like to store a
logical date rather than a timestamp. For example, he would like to
store the date 2008-09-28. The requirement being that the same date
is applicable to all timezones because it is composited from year/
month/day and is thus independent of timezones.
An example where this might be useful is to store birthdays.
Right - I think it was Florijan's more elaborate description that
confused me :-) I thought he was saying he wanted the date to be
presented according to the user's local timezone whilst at the same
time he was talking about this need. So I wasn't clear on his aims.
For example, a birthday is 1980-08-08. If I should decide to live in
Munich for a while (I presently live in Auckland) then the same
birthday applies, but if I stored it as a timestamp then it would
have shifted to another day while I live in Munich. Hence the
difficulty storing these things as timestamps.
Depends when you want your present ;-)
So if you're storing dates in the database (as opposed to timestamps)
you'll have to normalise them prior to storage. For display you'll
need a custom formatter.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden