| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
| Cc: | adrian(dot)klaver(at)gmail(dot)com, Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour |
| Date: | 2010-01-15 08:36:03 |
| Message-ID: | 162867791001150036u4abf855egeaa6ef85422d5f1e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> 3. Then I need to add the TABLE-level CHECK condition in order to
> exploit the "constraint_exclusion = on":
> execute $l2$
> alter table $l2$||ct||$l2$
> add check( $l0$||co||$l0$ )
> $l2$ using $l0$||va||$l0$;
>
I am sorry, I am out. Your code isn't much readable:
Minimally there isn't placeholder - some like $x
It is game for the most cryptografic code :).
You searching a functionality that isn't in pg now :(. Clause USING
doesn't work like macros or templates in C++
look on this page - maybe it could be useful for you
http://wiki.postgresql.org/wiki/Sprintf
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincenzo Romano | 2010-01-15 08:42:00 | Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour |
| Previous Message | Vincenzo Romano | 2010-01-15 07:51:10 | Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour |