From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: "stored procedures" - use cases? |
Date: | 2011-05-10 00:19:04 |
Message-ID: | 201105100019.p4A0J4Q11684@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kevin Grittner wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
> > what would be the actual use cases of any of these features?
> > Let's collect some, so we can think of ways to make them work.
>
> The two things which leap to mind for me are:
>
> (1) All the \d commands in psql should be implemented in SPs so
> that they are available from any client, through calling one SP
> equivalent to one \d command. The \d commands would be changed to
> call the SPs for releases recent enough to support this. Eventually
> psql would be free of worrying about which release contained which
> columns in which system tables, because it would just be passing the
> parameters in and displaying whatever results came back.
>
> I have used products which implemented something like this, and
> found it quite useful.
Uh, why does this require stored procedures? Seems our existing
function capabilities are even better suited to this.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-05-10 00:20:06 | Re: "stored procedures" - use cases? |
Previous Message | Bruce Momjian | 2011-05-10 00:15:23 | Re: Unfriendly handling of pg_hba SSL options with SSL off |