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: Pascal Robert <email@hidden>
- Date: Mon, 22 Dec 2008 15:34:12 -0500
Le 08-12-22 à 15:07, Chuck Hill a écrit :
On Dec 22, 2008, at 11:32 AM, Florijan Stamenkovic wrote:
Hi all,
I am recording daily currency conversion rates.
The problem I have is that at the moment currency information can
be input from wherever on the planet. Now, most users will deal
with date info only, when it comes to currency info, leaving time
and timezone issues in Java's hands. Java seems to automatically
set a parsed date to the time of 00:00:00 in the current timezone.
What I am thinking of is "normalizing" dates after input.
Essentially extracting the date (textually) from the Date that Java
parsed, and setting it to 12:00:00 GMT, in hope that will ease
qualification / filtering later on.
So, does anyone do this? Does anyone have a better strategy? This
is the first time I am doing stuff with dates requires tight
control of what's happening...
I do this, but I usually only work over 2-3 timezones. World wide,
this might still have some issues. I hate thinking about dates and
times. Bring on the goats!
http://www.macti.ca/ChuckAndDates.mov _______________________________________________
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