On Fri, 13 Feb 2009, Mindaugas Kavaliauskas wrote: Hi Mindaugas,
>> Sorry but it's not enough. >> But here we will have other problem .... > I do not know, that will be the end decision of this discussion, but I do > NOT see any good way to implement Time zones, or even Time offset in the > core of timestamp data typein some magic transparent way. > I think in many implementations (database field format, etc.) has just > timestamp without time zone, but it's programmers business to do a proper > conversion. Very well said. I hoped that someone will see it ;-) If I want to store UTC+0000 value then I simply use that time representation by using function which returns UTC time. If I need local time then I use function which returns local time. In theory it is possible to resolve this problem and keep everything internally in UTC and make online conversions. But in real life it cannot be easy implemented due to the fact well described in one of GNU man pages: ,------------------------------------------------------------------------- | Of course it turned out that the period in which Daylight Saving Time | is in force cannot be given by a simple algorithm, one per country; | indeed, this period is determined by unpredictable political decisions. `------------------------------------------------------------------------- Each time when I was writing about some automatic conversions I was thinking how to disable them for my own use ;-) I think it should finish the discussion about this feature until someone will not present complete and working solution which will not break the code already designed to work with different timestamp representations. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
