Re: BUG #2403: Date arithemtic using INTERVAL in UPDATE command - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2403: Date arithemtic using INTERVAL in UPDATE command
Date
Msg-id 6630.1145914323@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #2403: Date arithemtic using INTERVAL in UPDATE command  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: BUG #2403: Date arithemtic using INTERVAL in UPDATE command  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> That is definately a bug:
>     test=> SELECT INTERVAL '100' YEAR;

We don't currently support that style of specifying interval constants,
and you shouldn't hold your breath expecting it to happen --- it will
require a whole bunch of abuse of the currently data-type-independent
processing of literal constants.  I don't think anyone's even thought
about it since Tom Lockhart stopped working on that part of the code.
The fact that the syntax is accepted at all is just because he had
done some preliminary work on the grammar, but there's no infrastructure
behind the grammar for handling it.

In short, you need to calibrate your expectations as "feature addition
someday", not "bug fix".

> As a work-around until we fix it, please use:
>     test=> SELECT INTERVAL '100 year';

This is the syntax we support.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Volkan YAZICI
Date:
Subject: Re: BUG #2402: case insensitive match for unicode doesn't work
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #2403: Date arithemtic using INTERVAL in UPDATE command