From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Joel Jacobson <joel(at)trustly(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL 2 |
Date: | 2014-09-01 14:11:46 |
Message-ID: | CAFj8pRBCnSbRV3HD8zvO6iR-Ad5fKcd-rFEjM3m5fRbPzKfqCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2014-09-01 16:01 GMT+02:00 Craig Ringer <craig(at)2ndquadrant(dot)com>:
> On 09/01/2014 09:58 PM, Pavel Stehule wrote:
> >
> > It is in ToDo - allow parametrization for COMMANDs.
> >
> > But this is one point, when I am not sure if we would it. Now -
> > situation is very simply. Variables should not be used as table or
> > column name. With your proposal, the situation will by much more
> > complex, and probably variables should be used in SELECT * FROM x; but
> > it can be ambiguous SELECT x FROM table ... so maybe better to don't
> > allow it
>
> We would have to define a specific parameter marker, as used by things
> like JDBC.
>
> SELECT x FROM ?tablename
>
> DROP TABLE ?tablename
>
> or whatever your favourite place-holder syntax is.
>
It can be solution, but I dislike it .. It increase a language complexity
.. vars with or without prefix .. and more, hidden dynamic SQL
Nothing what I like - I have a mental barrier to this concept.
Pavel
>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-09-01 14:17:53 | Re: PL/pgSQL 2 |
Previous Message | Craig Ringer | 2014-09-01 14:01:33 | Re: PL/pgSQL 2 |