From: | Joshua <joshua(at)joshuaneil(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: simple plpgsql / sql function question |
Date: | 2008-03-11 18:02:17 |
Message-ID: | 47D6C929.3010503@joshuaneil.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks for the info. I will make sure to direct these types of questions
to the 'general' list in the future.
Thanks again for your help!!!
Merlin Moncure wrote:
> On Tue, Mar 11, 2008 at 1:26 PM, Joshua <joshua(at)joshuaneil(dot)com> wrote:
>
>> Hello,
>>
>> I have a series of SQL Update statements. I would like to write a
>> function which runs all of the SQL Update statements one at a time, in
>> order from top to bottom. Can somebody share the basic syntax that I
>> would need to write the aforementioned function?
>>
>
> please ask future questions of this nature on the general list. the
> hackers list is reserved for things pertaining to postgresql
> development.
>
> anywyays, the answer is easy:
> sql (imo preferred for this case):
> create function do_stuff returns void as
> $$
> update foo set bar = 1 where foo_id = 2;
> [repeat as necessary]
> $$ language sql;
>
> plpgsql:
> create function do_stuff returns void as
> $$
> begin
> update foo set bar = 1 where foo_id = 2;
> [repeat as necessary]
> end;
> $$ language plpgsql;
>
> merlin
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-03-11 18:07:27 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Previous Message | Tom Lane | 2008-03-11 18:02:09 | Re: [PATCHES] Fix for large file support (nonsegment mode support) |