Re: Stored Procedure Newbie - Mailing list pgsql-general

From Thalis A. Kalfigopoulos
Subject Re: Stored Procedure Newbie
Date
Msg-id Pine.LNX.4.21.0107101820270.7168-100000@aluminum.cs.pitt.edu
Whole thread Raw
In response to Stored Procedure Newbie  (chaconeric@hotmail.com (Eric Chacon))
List pgsql-general
On 6 Jul 2001, Eric Chacon wrote:

> I have a file with the following contents:
>
> DROP FUNCTION update_flag_func();
> CREATE FUNCTION update_flag_func()
> RETURNS text
> AS 'UPDATE update_flag SET content=current_timestamp;'
> LANGUAGE 'plpgsql';
>
> SELECT update_flag_func();
>
> When I run the 'UPDATE update_flag SET content=current_timestamp' in
> the SQL window (pgaccess), it works.
>
> When I type
> psql -f udt jags_content
>
> I get an error...
>
> DROP
> CREATE
> psql:udt:7: NOTICE:  plpgsql: ERROR during compile of update_flag_func
> near line 1
> psql:udt:7: ERROR:  parse error at or near "UPDATE"
>
> What obvious thing am I missing?

The way you do it, it's better you define LANGUAGE 'sql'
Plpgsql is supposed to have a BEGIN and an END surrounding the statements.

cheers,
thalis


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Stored Procedure Newbie
Next
From: simon@gonzo.magellic.com (simon lai)
Date:
Subject: Large table load (40 millon rows) - WAL hassles