[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] time representation
|
Hi,
I used NUMERIC(18,0) because I followed Postgre code as example and tried to use a number to keep the same schema.
There's no special reason for using NUMERIC(18,0) instead of TIMESTAMP.
Regards,
Rodolfo
On Wed, 2003-01-15 at 13:34, Dave Shields wrote:
We currently use integers to represent dates in the repository, measured
in milliseconds since 00:00:00 1 January 1970 GMT, also known as Unix "epoch" time.
Since 32 bits don't suffice, we have been using long (64 bit) integers. However, as
best I can tell Firebird doesn't support long integersr; Rodolfo's Firebird
code uses NUMERIC(18,0).
When running using Firebird Super Server against latest (today's) current build,
you will note a null pointer exception in LocalHandle that is probably due to
problem with time representation. This is a guess, as I haven't yet downloaded
the source for Jaybird driver.
If we must change to a different format, does anyone know of any reason *NOT* to use
TIMESTAMP?
dave
