I thought I saw somewhere that it was by design for 'NOW' to work this way.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Nando Dessena" <nandod@...>
To: <ib-support@egroups.com>
Sent: Monday, January 15, 2001 11:11 AM
Subject: [ib-support] How to extract milliseconds?


> Hello,
> I don't know if this is the right list, since I have a feeling that this
> post is more a bug report than a support question. Anyway...
>
> It seems to me that the following query (dialect 3)
>
> select extract(second from current_timestamp) from rdb$database
>
> will always return a whole number (milliseconds = 0).
> I have done a bit of tests, and it resulted that 'NOW' and
> CURRENT_TIMESTAMP will never return the correct number of milliseconds,
> whereas
>
> select extract(second from cast('12/12/2000 08.09.10.11' as timestamp))
> from rdb$database
>
> will return 10.1100 as expected.
> This happens on a W2k box.
> I would like to know if this is a bug or works as designed.
> Is it impossible to convey milliseconds information in all platforms?
> --
> ____
> _/\/ando
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>