From: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: using PQexecParams in psql (using variables as real params) |
Date: | 2009-11-16 05:46:09 |
Message-ID: | 20091116144609.7D78.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I propose to add possibility to use psql variables as real query
> parameters. The goal of this proposal is simplification of creating
> psql based commands.
> postgres=# \pexec
> Separately passing parameters is on.
> postgres=# select upper(:message);
There might be good if we can use both old and new behaviors at once
instead of \pexec switch. Something like:
SELECT * FROM :tablename WHERE id = $value
BTW, this proposal is a partial solution for scripting in psql.
But we will want other goodies soon - assignment, if, loop...
If there is a total solution, it would be better than a partial one.
I've heard pgAdmin uses pgScript as a client-side language.
Should we also take the language (or client-side plpgsql) in psql?
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-16 05:46:46 | Re: limit to default display in psql |
Previous Message | Tom Lane | 2009-11-16 05:44:00 | Re: ORDER BY vs. volatile functions |