| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Greg Sabino Mullane <greg(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl |
| Date: | 2010-02-16 18:12:40 |
| Message-ID: | 20100216181240.GK5330@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Richard Huxton wrote:
> On 16/02/10 17:51, David E. Wheeler wrote:
> >On Feb 16, 2010, at 9:43 AM, Richard Huxton wrote:
> >
> >>Perhaps it would be better to be explicit about what's going on?
> >> SEARCHPATH->function()
> >> SCHEMA('public')->function2()
> >>
> >>Or did "SP" mean "Stored Procedure"?
> >
> >Yes.
>
> Hmm - might be worth avoiding that in case we get actual
> transaction-spanning stored procedures at any point.
Yeah ... I used to get a lot of questions on the spanish list about
pgAdmin calling some functions "procedures" (just because they returned
void). While it may be technically true, it'd cause trouble if we ever
get around to supporting true procedures.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2010-02-16 18:22:00 | Re: Listen / Notify - what to do when the queue is full |
| Previous Message | Richard Huxton | 2010-02-16 18:07:36 | Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl |