Subject | Re: [firebird-support] Re: Record versioning/timestamping |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2004-12-21T07:17:54Z |
On 21 Dec 2004 at 5:39, Greg At ACD wrote:
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.
--
SY, Dimitry Sibiryakov.
>If the database can sort the dates using the milliseconds, that willI can say for sure that lack of milliseconds in your application is
>be part of the battle, but we will still need to show the milliseconds
>in the application. I suppose we could create another column to store
>the millisecond portion for display purposes. Still, its a hack and
>hopefully Firebird 2.0 will expose the millisecond support.
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.
>If I can't use timestamps to store the change indicator, i'll likelyDo it. Generator is much more reliable.
>just use a generator; it should work well for this anyway.
--
SY, Dimitry Sibiryakov.