From: | Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> |
---|---|
To: | Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> |
Cc: | Pascal Polleunus <ppo(at)beeznest(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: error when executing dynamic commands with transaction |
Date: | 2004-02-12 11:02:37 |
Message-ID: | 402B5D4D.7090007@frodo.hserus.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Shridhar Daithankar wrote:
> Pascal Polleunus wrote:
>
>> If I don't use a transaction in the executed statement, there is no
>> problem.
>> Remark: In this example a transaction is not needed, but in my real
>> usage of this I'm creating a table and granting permissions, and maybe
>> also creating a view. So a transaction is preferable.
>>
>> I've tested this on "PostgreSQL 7.4.1 on i386-pc-linux-gnu, compiled by
>> GCC i386-linux-gcc (GCC) 3.3.2 (Debian)", Debian Sarge.
>
>
> AFAIK, functions reside in transaction scope created by caller. So you
> can not call begin/commit in a transaction.
Argh.. read that as 'can not call begin/commit in a function'.
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wollny | 2004-02-12 11:07:08 | Re: Migrating 7.1.3 to 7.3.4 problem |
Previous Message | Pascal Polleunus | 2004-02-12 10:49:21 | Re: Is a capital letters title for this ML blocked? |