[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
[sqr-users] Is it possible - or advisable - to set a sql commit to1?
- Subject: [sqr-users] Is it possible - or advisable - to set a sql commit to1?
- From: Joe_Johnson@adp.com
- Date: Wed, 7 Apr 2004 15:09:04 -0500
- Delivery-date: Wed, 07 Apr 2004 15:29:40 -0500
- List-id: "This list is for discussion about the SQR database reportinglanguage from Hyperion Solutions." <sqr-users.sqrug.org>
Greets,
Thanks for the help, everyone.
Looks like I'll deal with this in the on-error procedure.
Joe Johnson
Programmer Analyst
ADP ESG - Technical Services Group
email: joe_johnson@adp.com
----- Forwarded by Joe Johnson/ESG/NAD on 04/07/2004 03:08 PM -----
Joe Johnson
To: sqr-users@sqrug.org
04/06/2004 12:53 cc:
PM Subject: Is it possible - or
advisable - to set a sql commit to 1?(Document link: Joe
Johnson)
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