From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ross Boylan <ross(at)biostat(dot)ucsf(dot)edu> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: how to call stored procedures that are writes |
Date: | 2012-05-31 05:23:56 |
Message-ID: | 28695.1338441836@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Ross Boylan <ross(at)biostat(dot)ucsf(dot)edu> writes:
> Suppose I have a function (stored procedure) whose purpose is to write
> to the database. How would I call the function from a client? select?
Yup. Functions are functions.
> It seems strange to use a select for something that writes rather than
> reads.
Perhaps. We have resisted adding a separate "CALL" type of command,
though, as long as it would only be syntactic sugar for calling the same
kind of function object. There has been a lot of discussion about
adding a different sort of stored procedure that would execute "outside"
rather than "within" the transaction engine, so that it could start and
commit multiple transactions; and if and when that happens, it would
need a different type of statement to call it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-31 05:35:17 | Re: could not access file "$libdir/plpgsql": No such file or directory |
Previous Message | Ross Boylan | 2012-05-31 00:52:46 | how to call stored procedures that are writes |