Re: using separate parameters in psql query execution

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: using separate parameters in psql query execution
Date: 2009-12-21 06:03:18
Message-ID: 162867790912202203u1e4fda7j5e0f7ba6c39c783a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/12/21 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Mon, Nov 16, 2009 at 5:01 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Hello
>>
>> now - complete patch
>>
>> ToDo:
>> * enhance a documentation (any volunteer?)
>> * check name for backslash command
>
> I read through this patch tonight and I don't understand what the
> point of this change is.  That's something that should probably be
> discussed and also incorporated into the documentation.

Do you ask about ToDo points?

I used "pexec" as switch. Probably better name is

"parametrized-execution", "send-parameters-separately" or "parametrized-queries"

general goal of this patch is removing issues with variables quoting
- using psql variables should be more robust and more secure.

I checked second design based on enhanced syntax -
http://www.postgres.cz/index.php/Enhanced-psql#Variables_quoting . It
working too, but it needs one exec more.

Regards
Pavel

>
> ...Robert
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-12-21 07:46:39 Re: Small Bug in GetConflictingVirtualXIDs
Previous Message Pavel Stehule 2009-12-21 05:48:15 Re: Proposal: Pre ordered aggregates, default ORDER BY clause for aggregates - median support