RE: [sqr-users] Is it possible - or advisable - to set a sql comm itto 1?

["Anderson, Paul S" <Paul.Anderson@usa.xerox.com>]

You shouldn't need commits... The following would execute 2-2-1-Insert-Error
on an insert error due to constraints etc..
and return for additional processing.

begin-SQL on-error=2-2-1-Insert-Error
INSERT INTO PS_JOB (

-----Original Message-----
From: sqr-users-bounces+paul.anderson=usa.xerox.com@sqrug.org
[mailto:sqr-users-bounces+paul.anderson=usa.xerox.com@sqrug.org] On Behalf
Of Joe_Johnson@adp.com
Sent: Tuesday, April 06, 2004 1:53 PM
To: sqr-users@sqrug.org
Subject: [sqr-users] Is it possible - or advisable - to set a sql commit to
1?



Greetings,

We have an interface that inserts rows of data into PS_JOB.

We have been asked to change the logic so when an insert error occurs, the
rest of the input file data can be inserted rather than have the process
stop with the insert error.

I'm thinking the only way to do this is to commit the insert after each row.

1)  Can this be done?  I am using begin-sql for the insert statement.

2)  What are the risks with this approach, besides, large overhead as each
row is committed?

Thanks,

Joe Johnson
Programmer Analyst
ADP ESG - Technical Services Group





_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org http://www.sqrug.org/mailman/listinfo/sqr-users

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users