Milan Babuskov wrote:

> Steffen Heil wrote:
>> First make sure, no employee is working during daylight saving switching. Firebird is unfortunately incapable of handling this correctly if you don't store you dates and times in utc (or any other timezone not having daylight savings). You will miss one hour per employee or get an additional hour...

Not just a Firebird problem ... many systems can't cope with daylight saving!
And until they fix the 'internet' your browser will add to the problem ;)

>> If you safe you dates and times in your timezone and this timezone contains daylight savings and you might have employees working at switching times, you need to do these calculations in your application, you cannot rely on firebird. (Note that you will also loose information!)
>> (Unfortunately, these restrictions seem inacceptable for any real life generic applications...)
>
> Alternative is to run your operating system time in UTC, store
> everything in Firebird in UTC and convert to local time for display/entry.

Daylight saving is the biggest reason for running UTC internally. Only locations
that do NOT have daylight saving can simply use 'server time'. but until we get
some agreement on how to tell people which daylight saving zone you are in .....

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php