> Hmm, I started this reply planning on arguing that _keeping_ the 'ago'
> was easiest on my ears. Now I find I've talked myself into losing it,
> because it implies too much: 'ago' claims that that one end of the
> interval is 'now' and the other end is in the past. If what you've got
> is actual
On Fri, Nov 03, 2000 at 04:25:23PM +, Thomas Lockhart wrote:
> I've been working on date/time issues over the last few weeks (at least
> one or two from reports on the list, others that I've stumbled across,
> and even one or two planned ones ;)
>
>
> Should we move to signed-only represent
I've been working on date/time issues over the last few weeks (at least
one or two from reports on the list, others that I've stumbled across,
and even one or two planned ones ;)
Anyway, the INTERVAL type output representation has trouble with values
such as
'-1 month +2 hours'
since it assum