> > 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.
> I realize having a local timezone option will result in a
> hornet's nest of adjustments for Daylight Saving Time etc...
As per previous messages, why bother? It is not a requirement for importing
data in ADO.NET.
Ludo
___
fpc-pascal maillist -
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
