Re: Transaction Logging without COMMITs

r_pastore@my-deja.com wrote: > > I understand that with code that does not have BEGIN WORK or COMMIT > statements (logging turned on), Informix inserts these statements > before and after each update SQL command. > My question, is considering the following code: > > .... > WHENEVER ERROR CONTINUE > DELETE FROM hrb_hold > WHERE hh_req = something > if status then > return FALSE > end if > ....> > Does the status reflect the 'DELETE' statement or the implied COMMIT? It is not that Informix inserts BEGIN WORK, COMMIT/ROLLBACK WORK statements around a singleton SQL it is just that the engine treats the statement as a singleton transaction unto itself. So the error reporting is for the SQL you execute (in this case the DELETE) since there IS no other statement to report on. Art S. Kagel

Thanks, that takes a load off my mind. We're migrating from SE to Online with logging and this is one less thing I don't have to worry about. Ray Pastore In article <3770FDF4.E079F4FC@bloomberg.net>, kagel@bloomberg.net wrote: > r_pastore@my-deja.com wrote: > > > > I understand that with code that does not have BEGIN WORK or COMMIT > > statements (logging turned on), Informix inserts these statements > > before and after each update SQL command. > > My question, is considering the following code: > > > > .... > > WHENEVER ERROR CONTINUE > > DELETE FROM hrb_hold > > WHERE hh_req = something > > if status then > > return FALSE > > end if > > ....> > > > Does the status reflect the 'DELETE' statement or the implied COMMIT? > > It is not that Informix inserts BEGIN WORK, COMMIT/ROLLBACK WORK > statements around a singleton SQL it is just that the engine treats the > statement as a singleton transaction unto itself. So the error > reporting is for the SQL you execute (in this case the DELETE) since > there IS no other statement to report on. > > Art S. Kagel > Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.