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? The DELETE. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>

Thanks, that makes sense. Ray In article <377167AC.159A@earthlink.net>, jleffler@earthlink.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? > > The DELETE. > > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h> > > Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.