| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Joel Jacobson <joel(at)trustly(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-09 14:14:14 |
| Message-ID: | CAFj8pRA3Uqg3iRiQEerKXft6AFv-M7XjNZnFeG-eSieRgdto8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
>
> Real support for using variables as identifiers / nothing restricted to
> only accepting a Const.
>
This point is problematic not only from performance perspective.
if you don't use some special syntax and you allow variables as identifier,
then you will got a ambiguous situation quickly - although variables can
have special symbol prefix
SELECT * FROM tab WHERE $var1 = $var3
What is $var1, what is $var2? identifier or value?
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2017-01-09 15:02:54 | Re: WIP: Covering + unique indexes. |
| Previous Message | Dilip Kumar | 2017-01-09 13:52:19 | Re: Parallel bitmap heap scan |