| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Martin Gainty <mgainty(at)hotmail(dot)com> |
| Cc: | stark(at)enterprisedb(dot)com, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Pet Peeves? |
| Date: | 2009-01-30 06:09:29 |
| Message-ID: | 49829999.5070000@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martin Gainty wrote:
> PROCEDUREs *which compile into Procedure Cache* and have IN/OUT (Mode) parameters..
Do you mean that as a feature request?
If you intended to say something along the lines of: "I'd like stored
procedures, invoked using 'CALL procname(params)' syntax, as distinct
from SQL or PL/PgSQL functions" ... then I do agree that'd be handy.
Their absence could easily become a peeve, especially if you use DB
interfaces that expect to invoke stored procedures this way. Some seem
to want you to jump through some hoops (switch to "native query" mode,
declare functions to the interface, etc) to call server-side functions,
but provide a convenient interface to CALL stored procedures.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-01-30 07:55:38 | Re: md5 doesn't work (Was Re: Pet Peeves?) |
| Previous Message | Martin Gainty | 2009-01-30 04:07:00 | Re: Pet Peeves? |