| Subject | RE: [ib-support] Insert Data which not canceled if something wrong like violation on unique index |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-01-13T08:22:34Z |
At 02:54 PM 13/01/2003 +0700, you wrote:
procedure. If you are processing each insert in a loop inside a SP, have
the code jump out to an exception handling block (ON <error code> DO) and
swallow the exception in whatever way you like. As soon as your exception
handling completes, control will pass back into your loop, at the line
after that where the exception occurred.
<error code> can be: an SQLCODE, a GDSCODE or a user-defined exception.
Grab the TI Sheet on exception handling from www.ibobjects.com/TechInfo.html.
AND PLEASE DO NOT CROSS-POST TO MULTIPLE LISTS.
^heLen
>Well,This is a case where you need to use exception handling in your stored
>
>Actually, i just pumping/copy data from the same FB databases to another
>table and i execute this via stored procedure.
>Reason using SP is, the data on server is about thousand record in every
>pumping.
>
>Is there any setting on the connection or ib_query ( we using IBO )
procedure. If you are processing each insert in a loop inside a SP, have
the code jump out to an exception handling block (ON <error code> DO) and
swallow the exception in whatever way you like. As soon as your exception
handling completes, control will pass back into your loop, at the line
after that where the exception occurred.
<error code> can be: an SQLCODE, a GDSCODE or a user-defined exception.
Grab the TI Sheet on exception handling from www.ibobjects.com/TechInfo.html.
AND PLEASE DO NOT CROSS-POST TO MULTIPLE LISTS.
^heLen