Hi,

> If I am using time as milliseconds since epoch and not doing any
> special queries with it, is there any advantage to using a TIMESTAMP
> field over a NUMERIC(18,0) field? My object stores the value as a long
> (from System.currentTimeMillis()) and it seems a bit of a drag to
> constantly create Timestamp instances from that long when saving or
> call .getTime() on the timestamp object when loading. Thoughts?

I think you will loose the possibility to use SQL to manipulate date
(e.g. EXTRACT YEAR, etc.). If you are sure you can live with it, I see
no problems. Also, are you sure that object creation time is so
crucial to your application that you have to look for an optimization
in this part of your application?

But you should also ask in Firebird-Support group, all database gurus
live there.

Regards,
Roman