If you want to realize your insert chain in plpgsql, trapping exceptions
is a good idea, imho. But I am not experienced with these new features
in pg 8.0 ...
Surabhi Ahuja wrote:
cant the same be done by trapping the errors. by trapping these
exceptions?
http://www.postgresql.org/docs/8.0/interactive/plpgsql-control-structures.html
search for "trapping errors" ?
------------------------------------------------------------------------
*From:* Jan Poslusny [mailto:pajout@xxxxxxxxxxxx]
*Sent:* Tue 2/8/2005 3:30 PM
*To:* Surabhi Ahuja
*Cc:* pgsql-general@xxxxxxxxxxxxxx
*Subject:* Re:
***********************
Your mail has been scanned by InterScan VirusWall.
***********-***********
You can use savepoints in pg 8.0:
http://www.postgresql.org/docs/8.0/static/sql-savepoint.html
Surabhi Ahuja wrote:
> in a transaction i try to insert into a table1, followed by insert
> into table 2 then insert into table 3 and last insert into table 4.
> However if a unique key violation occurs in the table 1 , the whole
> trabnsaction aborts. is there no way , where i can ignore this
> violation, and continue with the remaining insertions.
> ?
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
