Re: [Virtuoso-users] Scope of log_enable and effect on deletes

Hi Daniel, What Virtuoso open source or commercial release and build date or git tree are you using / building from ? I don’t understand how your first query reports 4393 subjects and then in your last statement you say there should be 2 million ? What is the total triple count of the

Re: [Virtuoso-users] Scope of log_enable and effect on deletes

Thanks, Quentin. Then it is not the log setting. When I try to trouble-shoot in a new connection (isql rather than perl DBI over ODBC), I observe very odd results indeed: SQL> sparql select count(*) from where { ?s a ?o }; … 4393 SQL> sparql clear graph

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 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

[Virtuoso-users] Scope of log_enable and effect on deletes

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