>
> You keep on talking about "time" in real life and how this has been
> agreed upon (or not agreed upon) etc...
>
> I keep on talking about the TIME datatype, which is what the issue
> is about. Don't you see the difference?
>

TIME datatype is work as designed and fits requirements as neeeded,
Martijn.
It keeps any duration from first second to last second in its limits.
If 24H fits your work, you can use it.
You may not want to use TIMESTAMP if your TIME infos don't want/care
the calendar system.
TIME datatype works perfectly for me.
I can't say this for TIMESTAMP, because it stores
values with some arbitrary restrictions, calendar is a playable info,
it works irregular.

Finally, i didn't understand your problem with TIME datatype.

Regards.
Ali