From: | Andrei Kovalevski <andyk(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PREPARE vs query with MULTIPLE statements |
Date: | 2007-11-21 06:10:46 |
Message-ID: | 4743CBE6.5070705@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yes, Thank you!
Tom Lane wrote:
> Andrei Kovalevski <andyk(at)commandprompt(dot)com> writes:
>
>> 2) If I send it as 'PREPARE "SQL_CUR1" AS SELECT 1; SELECT 2; SELECT3;
>> SELECT4;' and then 'EXECUTE "SQL_CUR1" - I'm getting:
>> - results for SELECT 1; SELECT2; SELECT 3;
>> - ReadyForQuery response
>> - results for SELECT 4;
>> - one more ReadyForQuery response
>> from backend
>>
>
>
>> Is this behavour is correct and expected?
>>
>
> You seem to have some odd ideas about what the semicolons mean.
> The prepare command there is PREPARE "SQL_CUR1" AS SELECT 1
> ... no more and no less.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
From | Date | Subject | |
---|---|---|---|
Next Message | B. Maust | 2007-11-21 07:23:38 | plperl failure on OS X 10.5(.1) |
Previous Message | Tom Lane | 2007-11-21 05:57:35 | Re: PREPARE vs query with MULTIPLE statements |