> It might work right now, but maybe later (in later FB version or

later

> versions of your database acces components) TIME won't allow, for
> example, a value like "39:20:35" meaning 39 hours, 20 minutes and

35

> seconds (does it allow such a value now?). It might/should be

restricted

> to the interval 00:00:00 through 23:59:59. If you have a "time of
> process" that's longer than one day, how would you store that in

such a

> strict TIME column?
>
> And don't tell me that it's ok because that's just "1 day, 15

hours, 20

> minutes and 35 seconds", because then you've sgtarted mixing dates

into

> it, and that *will* cause you problems (leap years, months of

nonequal

> lengths and so forth).
>
> A DURATION on the other hand, *would* support durations of

arbitrary

> length, counted in days and fractions thereof.
>
> Kjell
> --

Oh GOD!

When did i say as i want to store "39:20:35" ??!!!

It was Martijn, he told about a new datatype for time calculation.

I said TIME is perfect because of it is restricted as 24H.

I said TIME is perfect because it is stabil.

I am a retired programmer,
never mind me here, and help to Arnaldo please. ;)

Regards.
Ali