On 25-7-2011 11:57, Ludo Brands wrote: >>> That is also what most of the underlying databases do. They store >>> everything in UTC and convert to local time. Only for those that >>> support "timezoned" field types (fe. oracle timestamp_TZ) you can >>> specify a timezone when entering data. MySQL fe. doesn't >> have support for this. >>> >>> Ludo >>> >> >> Mmmm. For example, IIRC, Firebird just stores it as entered - >> no UTC conversion. Sensible developers on multi country >> Firebird db projects would probably store convert date/time >> info to UTC in the database. >> > > I'm talking about internal database storage. On the binary level. If you > move a database to a system with a different timezone the dates display > differently when stored internally in UTC. > > Ludo I understand.
If I remember correctly, Firebird just stores date/time as some bits. AFAIR, it doesn't convert any given times to/from UTC when storing/retrieving times. I'm not willing to play around with timezones and Firebird right now, though ;)... _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
