Sorry but it's not enough.
...
But here we will have other problem ....
Hi,
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. If we try to do employers work time registration,
perhaps we will save local time in database and we will not play with
different UTC offsets for summer and winter. If we are going to do air
traffic controller database we will use UTC only (despite of place on
earth we are working). If we try to collect some time sensitive
astronomical data, we may need to pay a huge attention on leap seconds
(http://en.wikipedia.org/wiki/Leap_second).
We just have to know that system our database {, "T", 8, 0} field is,
and have a function to know different between local time and time on
THAT system. In many cases information about time difference between
local and UTC is enough. It programmers job to convert it to required
time offset for some database, or network protocol.
Regards,
Mindaugas
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
