...Roll Back issue in PGSQL..
Hi
I am trying to create a TRIGGER function,that populates values to another
table upon inserting a value into a table. The issue is,if there is a
exception(in Table 2) everything gets rolled back including Table1.I dont
want this to happen.i want the value of table1 to stay.
I tried "try....except" and introduced SAVEPOINT.But resulted in runtime
error.
Can anyone please help me out
--
Deepak
Import Notes
Reply to msg id not found: f60059d0806180551t52ec047fpa40a58c2fa7de77a@mail.gmail.comReference msg id not found: f60059d0806180551t52ec047fpa40a58c2fa7de77a@mail.gmail.com
On Fri, 2008-06-20 at 13:10 +0530, Deepak wrote:
Hi
I am trying to create a TRIGGER function,that populates values to
another table upon inserting a value into a table. The issue is,if
there is a exception(in Table 2) everything gets rolled back including
Table1.I dont want this to happen.i want the value of table1 to stay.
I tried "try....except" and introduced SAVEPOINT.But resulted in
runtime error.Can anyone please help me out
The function executed by the trigger will be executed as a single
transaction. If any part fails, they all fail.
Joshua D. Drake
Show quoted text
--
Deepak
On Friday 20 June 2008 12:19:03 Joshua D. Drake wrote:
On Fri, 2008-06-20 at 13:10 +0530, Deepak wrote:
Hi
I am trying to create a TRIGGER function,that populates values to
another table upon inserting a value into a table. The issue is,if
there is a exception(in Table 2) everything gets rolled back including
Table1.I dont want this to happen.i want the value of table1 to stay.
I tried "try....except" and introduced SAVEPOINT.But resulted in
runtime error.Can anyone please help me out
The function executed by the trigger will be executed as a single
transaction. If any part fails, they all fail.
Well, wrapping the bits of table2 in a begin....exception block would allow
him to do what he wants.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL