> > No, but this is why I said that computations on TIME cannot
> > be done with a TIME format. For example, adding 10 hours
> > to 18:00 will give you 28 hours, which cannot be done in a
> > TIME datatype.
>
> hah! this posibility valid for all datatypes Martijn.
>
> for example:
> add 10 to 32758 for a smallint field.
> or 54321*54321 for a integer field.
> if you want to do this you should move 54321 value to a BIGINT.
> also bigint has a limit too.
> only the requirements are limitless. :P

I disagree. TIME is a specific domain.

> So, TIME is a special numeric field that
> can handle numbers between 0 and 86399, time is perfect becuse of
> this.

See above. It's not a "special numeric field", it's a TIME type.

Why is this different? Because the TIME type actually means
something. How this is solved internally (albeit via a 0..86399 numeric
field or as string or pieces of rock on a wooden board) is not
important.

There simply is NO such thing as 28:00 in a TIME type.

This is where TIME is different from "smallint" to "bigint".

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com