Re: R: Re: Weird EXECUTE ... USING behaviour
От | Adrian Klaver |
---|---|
Тема | Re: R: Re: Weird EXECUTE ... USING behaviour |
Дата | |
Msg-id | 201001130647.29947.adrian.klaver@gmail.com обсуждение исходный текст |
Ответ на | R: Re: Weird EXECUTE ... USING behaviour (Vincenzo Romano <vincenzo.romano@notorand.it>) |
Ответы |
Re: R: Re: Weird EXECUTE ... USING behaviour
|
Список | pgsql-general |
On Tuesday 12 January 2010 9:38:06 pm Vincenzo Romano wrote: > The static binding worked fine in the second EXECUTE USING statement but > not in the first one. > I still think that it's weird more than wishful. > I can work it around, though. > > Il giorno 12 gen, 2010 4:13 p., "Tom Lane" <tgl@sss.pgh.pa.us> ha scritto: > > Vincenzo Romano <vincenzo.romano@notorand.it> writes: > > I don't think so. Those variables should be evaluated with the USING > > > *before* the actual executi... > Unfortunately, that's just wishful thinking, not how EXECUTE USING > actually works. > > regards, tom lane Without the whole function it is hard to say. Given the error I would say it is a quoting issue. The table name is being substituted for, the other parameters are not. It acts like the add_check clause is not part of the EXECUTE statement and is just being passed through verbatim. ERROR: there is no parameter $1 CONTEXT: SQL statement " alter table public.test_part_2 add check( data>=$1::timestamp and data<$2::timestamp and maga=$3 ) -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-general по дате отправления: