From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | Daniel Caune <daniel(dot)caune(at)ubisoft(dot)com> |
Cc: | Owen Jacobson <ojacobson(at)osl(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Does PostgreSQL support job? |
Date: | 2006-02-02 14:16:45 |
Message-ID: | 43E2144D.4030901@logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi, Daniel,
Daniel Caune wrote:
> I'm not sure to understand. Why calling a function from a script is different from executing a series of SQL commands? I mean, I can run a script defined as follows:
>
> SELECT myjob();
>
> where myjob is a stored procedure such as:
>
> CREATE OR REPLACE FUNCTION myjob()
> RETURNS void
> AS $$
> <a-lot-of-complex-stuff-here>
> END;
> $$ LANGUAGE PLPGSQL;
>
> Does that make sense?
It does make sense if myjob() does more than just execute a bunch of
statements, e. G. it contains if(), loops or something else.
PLPGSQL is turing complete, plain SQL is not.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Caune | 2006-02-02 14:19:25 | Re: Does PostgreSQL support job? |
Previous Message | christian.michels | 2006-02-02 08:49:42 | Re: executing dynamic commands |