.
-Original Message-
From: Hugh Williams [mailto:hwilli...@openlinksw.com]
Sent: Tuesday, February 21, 2017 5:13 PM
To: Davis, Daniel (NIH/NLM) [C]
Cc: virtuoso-users@lists.sourceforge.net
Subject: Re: [Virtuoso-users] Scope of log_enable and effect on deletes
Hi Daniel,
What Virtuoso open
t; …
> 4
>
> If no delete has ever been done, the number of subjects remaining should
> almost 2 million – 1994719.
>
>
> From: Quentin [mailto:quentin@guidinghand.solutions]
> Sent: Tuesday, February 21, 2017 1:41 PM
> To: virtuoso-users@lists.sourceforge.net
&
guidinghand.solutions]
Sent: Tuesday, February 21, 2017 1:41 PM
To: virtuoso-users@lists.sourceforge.net
Subject: Re: [Virtuoso-users] Scope of log_enable and effect on deletes
From the manual:
>While log on and off setting alone is reset at the end of the transaction so
>that one does no
>From the manual:
>While log on and off setting alone is reset at the end of the transaction so
>that one does not end up with logging disabled by accident, the row-by-row
>autocommit mode causes the setting to be permanent inside the calling
>connection or web request. That is, for a SQL c
I am not sure I understand the scope of the log_enable() procedure.If I
call log_enable(2,1); in a stored procedure, I am sure that it will affect the
entire connection, but, will it affect other connections as well. Would it,
for instance, persist until reboot and affect other connections
