On Tue, 4 Apr 2006, Arí Ricardo Ody wrote:

Alright Michael. The fact is that there is tables that have TIMESTAMP columns with more than 3 digits of fraction... I'm trying to say that I think that you can't ignore it with simplicity. Or can you?

No, you have a point there.

But it will be rarely used, since no other engine I know of has this type.

(maybe oracle, but I don't know about that)

I trying to explain since this discussion starts that, at least, Lazarus/FPC can be able to handle 6 digits of fraction. Otherwise in can't process tables generated from some other languages(cobol, for example). Or you can create a Lazarus/FPC TIMESTAMP version.... :-[

We'd need a TPrecisionDateTime or TNanoDateTime;
It would be an Int64 or so, with the number of
nanoseconds since 1/1/1900; Int64 should be enough to store that.
But definitely not text.

Michael.

Reply via email to