Re: Bug #443: Problem with time functions.

> > Hmm. The underlying math works:
...
> "Works" is in the eye of the beholder, perhaps.

Of course ;)

> ... I would think that the
> difference of two times should be an interval (which would allow the
> sum() to work, since we have sum(interval)).  But there is no
> time-minus-time operator.  What actually appears to be happening is that
> the system casts the second time to an interval and then applies the
> time-minus-interval operator, yielding a time.  There is no sum(time)
> aggregate, and shouldn't be IMHO.
>
> In short, I think the missing piece is not sum(time) but
> time-minus-time.  Maybe that's what you think too, but it wasn't clear.

Well, I'd have been willing to think that, if I had known that.

> BTW, I'm unconvinced that an implicit cast from time to interval is a
> good idea... what's the point of maintaining a datatype distinction
> between timestamp-like types and interval-like types if we will allow
> implicit casts across that boundary?

I'm not certain whether this was to fix a particular issue or just
proactive mucking around.
Either way, a time-time operator seems like a good idea, until proven
otherwise. Will try to get it on my list for the current work.

                       - Thomas