| From: | "Daniel Caune" <daniel(dot)caune(at)ubisoft(dot)com> | 
|---|---|
| To: | "Markus Schaber" <schabi(at)logix-tt(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:19:25 | 
| Message-ID: | 1E293D3FF63A3740B10AD5AAD88535D201755A97@UBIMAIL1.ubisoft.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-sql | 
> > 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.
> 
Yes, indeed, that was the idea!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-02-02 14:19:26 | Re: Changing the transaction isolation level within the stored | 
| Previous Message | Markus Schaber | 2006-02-02 14:16:45 | Re: Does PostgreSQL support job? |