On 10/20/07, yogesh <yogesh.arora.daffodil@xxxxxxxxx> wrote:
> On Oct 19, 11:05 pm, scott.marl...@xxxxxxxxx ("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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
