Hi

> Here is the reason: We have a reporting tool ... retrieving date, time and

portions of datetime fields in spanish.

Use your own conversion functions and forget about firebirds time formatting
or parsing. You can all date/time fields, but you need to store the
information therein in utc time or any timezone that has no daytime
switching.
Otherwise firebird will break your reports during the switch from summertime
to wintertime. Then you also need to forget about build-In functions that
extract month or day values and such and even forget about
current_timestamp.

I am just investigating this myself for my projects and I currently see no
other way then to either force the server to be configured to utc or drop
all clean field formats and restrict me to bigints as client-interpreted
timestamps (for example javas 'milliseconds since 1.1.1970 0:00 utc).
Makes my application not really more complex and even faster (as jaybirds
date/time/timestamp functions are way from optmal), but is really really bad
if I need to have a look at the data myself (debugging) or if other software
shall access the same database.

Regards,
Steffen



[Non-text portions of this message have been removed]