--- In firebird-support@yahoogroups.com, "Dimitry Sibiryakov"
<SD@t...> wrote:

> I can say for sure that lack of milliseconds in your application

is

>an issue of component set / routine you use. All components that I
>know use isc_decode_timestamp() to convert timestamp from IB format
>to application format. But it converts timestamp to struct tm which
>does not support milliseconds. That's why I had to implement my own
>conversion routines in my application.
> Dmitry Yemanov fixed CURRENT_TIME and CURRENT_TIMESTAMP to return
>milliseconds in FB 2.

I am using SQLAPI (www.sqlapi.com), which does implement an
Interbase/Firebird layer as well. They are using isc_decode_date()
which of course is the older version of isc_decode_timestamp(), and
yes, it returns a struct tm, so no milliseconds are returned.
Therefore I would look at doing something similar to you and
implement my own routines; the millisecond portion is important for
us, and I'd rather find a way to deal with it rather than use
another DB solution (there are many aspects of Firebird that I like;
this is the first major roadblock I've come across).

Of course I do need to ask... is such an implementation already
publicly available (so to avoid the reinventing of the wheel...)?
Will FB 2.0 provide a new isc_decode_timestamp() function to support
milliseconds (and similarly for encoding)...?

Thx!

Greg