Hi Daniel, log_enable (2,1) would turn off transaction logging for the next statement executed which on completion the transaction logging would be turned back on.
If it is called in a stored procedure then once again it would turn off transaction logging for the next statement executed which on completion the transaction logging would be turned back on. Best Regards Hugh Williams Professional Services OpenLink Software, Inc. // http://www.openlinksw.com/ Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers > On 27 Oct 2015, at 13:53, Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov> > wrote: > > When I execute log_enable(2,1) in a session, does it just affect statements > made by that statement, or the whole server? > When the session closes, does it revert to logging transactions? > > What if I move log_enable(2,1) to a stored procedure called by a session? > > Dan Davis, Systems/Applications Architect (Contractor), > Office of Computer and Communications Systems, > National Library of Medicine, NIH > > ------------------------------------------------------------------------------ > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > <mailto:Virtuoso-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > <https://lists.sourceforge.net/lists/listinfo/virtuoso-users>
------------------------------------------------------------------------------
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
