| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Rob Richardson <RDRichardson(at)rad-con(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: What is a DO block for? |
| Date: | 2013-05-23 17:23:32 |
| Message-ID: | 519E5094.6010803@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 05/23/2013 05:58 AM, Rob Richardson wrote:
>
> Greetings!
>
> Another post on this list suggested using a DO block if the user's Postgres version is 9.0 or later. The documentation for the DO block says what it is, but not what it is for. The only benefit I could see for it is allowing the use of locally defined variables. I'm sure there's more to it than that. What justifies the existence of the DO block?
>
> The message that mentioned the DO block is quoted below as an example.
In database processing without having to create a function that is stored.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sajeev Mayandi | 2013-05-23 17:45:52 | Re: Rule for all the tables in a schema |
| Previous Message | fburgess | 2013-05-23 17:21:28 | Re: [PERFORM] Very slow inner join query Unacceptable latency. |