Ross Boylan <ross@biostat.ucsf.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
