Re: Calling Functions and Stored Procedures

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
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-15 16:46:26
Message-ID: 1089909986.1432.3.camel@braydb
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Thu, 2004-07-15 at 16:43, Mark Dexter wrote:
...
> 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?

No, you always use SELECT to call a function.

For example, to change the value of a sequence (using a built-in
function):

SELECT nextval('table_field_seq',553);

Oliver Elphick

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Yves 2004-07-15 17:57:44 postgres account default password
Previous Message Oliver Fromme 2004-07-15 16:36:31 Re: Extended query: prepared statements list?