From: | "Scott Marlowe" <smarlowe(at)qwest(dot)net> |
---|---|
To: | "Mark Dexter" <MDEXTER(at)dexterchaney(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Calling Functions and Stored Procedures |
Date: | 2004-07-18 22:39:12 |
Message-ID: | 1090190352.3429.24.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, 2004-07-14 at 19:21, Mark Dexter wrote:
> I understand that functions in Postgres server the purpose of both
> functions and stored procedures in other db's (e.g., MSSQL and
> Oracle). In these other databases, you call a stored procedure with
> different syntax (e.g., CALL <procedure name>) instead of using it in
> line in a SELECT statement.
>
> My question is this: If I write a Postgres function that is not
> designed to be part of a query (e.g., it should just do something), do
> I still use a SELECT statement to execute the function? Is there some
> other syntax that is the equivalent to CALL or EXEC?
Nope, you still use the select function() syntax for that too.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-07-19 04:05:48 | Re: SQL - Indexing for performance on uniquness check... |
Previous Message | Oliver Elphick | 2004-07-18 22:13:48 | Re: Function compile error |