You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2016/10/28 08:54:57 UTC
svn commit: r1000043 - in /websites/staging/jena/trunk/content: ./
documentation/tdb/faqs.html
Author: buildbot
Date: Fri Oct 28 08:54:56 2016
New Revision: 1000043
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb/faqs.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 28 08:54:56 2016
@@ -1 +1 @@
-1765142
+1766978
Modified: websites/staging/jena/trunk/content/documentation/tdb/faqs.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb/faqs.html (original)
+++ websites/staging/jena/trunk/content/documentation/tdb/faqs.html Fri Oct 28 08:54:56 2016
@@ -270,7 +270,7 @@ the other process is not accessing the T
database was eligible to be locked but wasn't. This can usually only occur if you circumvented the normal TDB database opening procedures somehow.</p>
<p>As the warning states data corruption may occur if another JVM accesses the location while your process is accessing it. Ideally you should follow the
advice on <a href="#multi-jvm">multi-JVM usage</a> if this might happen, otherwise the warning can likely be safely ignored.</p>
-<h2 id="windows-dataset-delete">Deleting Datasets on MS Windows<a class="headerlink" href="#windows-dataset-delete" title="Permanent link">¶</a></h2>
+<h2 id="windows-dataset-delete">Why can't I delete a dataset (MS Windows/64 bit)?<a class="headerlink" href="#windows-dataset-delete" title="Permanent link">¶</a></h2>
<p>Java on MS Windows does not provide the ability to delete a memory mapped
file while the JVM is still running. The file is properly deleted when the
JVM exits. This is a known issue with Java.<br />