Re: Trigger AFTER UPDATE OR INSERT - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Trigger AFTER UPDATE OR INSERT
Date
Msg-id dcc563d10710210718h4c9dd9efpd81108206105b342@mail.gmail.com
Whole thread Raw
In response to Re: Trigger AFTER UPDATE OR INSERT  (yogesh <yogesh.arora.daffodil@gmail.com>)
Responses Please help (backup)  (Anibal David Acosta <aa@personal.net.py>)
List pgsql-admin
On 10/20/07, yogesh <yogesh.arora.daffodil@gmail.com> wrote:
> On Oct 19, 11:05 pm, scott.marl...@gmail.com ("Scott Marlowe") wrote:
> > Yes, it's right.  Triggers are part of a transaction (or run their
> > own) so if the trigger fails, so does the transaction.
> >
> > If you really need to have something insert rather or not the
> > transaction succeeds, you can either use savepoints so that you can
> > roll back to before the error then insert the row anyway, or use
> > dblink to connect to the db through another backend and commit your
> > data that way.
> >
> > You might want to give more info on exactly what you're trying to do
> > so the folks on the list can make better informed recommendations.

> Hello Scott,
> Thanks to you....
>    you got the right point point what i want to know.......
>
>  are you saying about programming or any other way to done
> it........to insert a row even if the Trigger fails or succeeds

Read up on savepoints here:
http://www.postgresql.org/docs/8.2/static/sql-savepoint.html

pgsql-admin by date:

Previous
From: yogesh
Date:
Subject: Postgres SQL with Suse Linux
Next
From: Anibal David Acosta
Date:
Subject: Please help (backup)