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:25:32 |
Message-ID: | 43E2165C.1000409@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?
[snip]
>>>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.
> Yes, indeed, that was the idea!
There's another reason: For updating the cron job SQL commands, you need
root access (or at least shell access) to the database machine. For
updating a stored procedure, you need just the appropriate rights in the
database.
On larger deployments, this can be an important difference.
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 15:21:24 | Re: Does PostgreSQL support job? |
Previous Message | Markus Schaber | 2006-02-02 14:19:26 | Re: Changing the transaction isolation level within the stored |