Yes,I think this trigger an error is reasonable.It take me 2 hours to find
the problem,not friendly.
Jov
blog: http:amutu.com/blog <http://amutu.com/blog>
2015-12-08 14:08 GMT+08:00 David Gould <daveg@sonic.net>:
> On Tue, 08 Dec 2015 03:54:44 +0000
> amutu@amutu.com wrote:
>
>
> > execute $$select ('$1 month')::interval $$ into rt2 using n;
> > raise notice 'rt2 : %',rt2;
> >
> > execute $$select ($1::varchar || ' month')::interval $$ into rt2 using =
n;
> > raise notice 'rt2 : %',rt2;
> > end;
>
> > NOTICE: rt2 : 1 mon-----wrong=EF=BC=8Cshould 4 mons
> > NOTICE: rt2 : 4 mons
>
> You may have found a bug, but if so, it is not where you think it is. The
> expression: '$1 month' is a text literal. PL/PGsql does not interpolate $=
n
> like a shell, it only does the substitution where a variable could
> ordinarily exist.
>
> However, it does seem a little odd that the literal syntax for
> intervals accepts the '$':
>
> postgres=3D# select '$1 month'::interval, '$4 month'::interval;
> interval | interval
> ----------+----------
> 1 mon | 4 mons
> (1 row)
>
> I would have expected it to raise an error. The documentation does not sh=
ed
> any light on this. Anyone?
>
> -dg
>
> --
> David Gould 510 282 0869 daveg@sonic.net
> If simplicity worked, the world would be overrun with insects.
>
