On 09/06/2014 01:10, Hugh Williams wrote:
Hi Christophe.
Hi and thanks for your reply
I observe the same behaviour performing these steps against the latest
develop/7 git archive, thus we shall have to look into this.
ok happy to see that i'm not the only one to have this problem :/
I presum
Hi Jason,
This problem has been fixed in the open source git develop/6 branch, see:
http://sourceforge.net/p/virtuoso/virtuoso-opensource/ci/56f47f979572ce0ed0d09fb136658b093d23259e/
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www
Hi Bart,
Virtuoso uses read committed isolation level by default, such that no read will
block waiting for a lock held by another client, see:
http://docs.openlinksw.com/virtuoso/virtuosofaq.html#virtuosofaq30
Locks can be monitored using the Virtuoso sys_l_stat view as detailed at:
