svn commit: r875890 - in /websites/staging/jena/trunk/content: ./ documentation/jdbc/drivers.html

[bu...@apache.org]

Author: buildbot
Date: Fri Aug 23 19:49:53 2013
New Revision: 875890

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/jdbc/drivers.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug 23 19:49:53 2013
@@ -1 +1 @@
-1517000
+1517004

Modified: websites/staging/jena/trunk/content/documentation/jdbc/drivers.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/jdbc/drivers.html (original)
+++ websites/staging/jena/trunk/content/documentation/jdbc/drivers.html Fri Aug 23 19:49:53 2013
@@ -171,12 +171,40 @@ after the connection has been establishe
 <li><a href="#remote-endpoint">Remote Endpoint</a></li>
 </ul>
 <h3 id="in-memory">In-Memory</h3>
-<p>The in-memory driver provides access to a non-persistent memory dataset.  This dataset
+<p>The in-memory driver provides access to a non-persistent in-memory dataset.  This dataset
 may either be initially empty or may be initialized from an input file.  Remember that
 this is non-persistent so even if the latter option is chosen changes are not persisted
 to the input file.  This driver is primarily intended for testing and demonstration
 purposes.</p>
+<p>Beyond the common parameters it has two possible connection parameters.  The first of these
+is the <code>dataset</code> parameter and is used to indicate an input file that the driver will
+initialize the in-memory dataset with e.g.</p>
+<div class="codehilite"><pre><span class="n">jdbc</span><span class="o">:</span><span class="n">jena</span><span class="o">:</span><span class="n">mem</span><span class="o">:</span><span class="n">dataset</span><span class="o">=</span><span class="n">file</span><span class="o">.</span><span class="na">nq</span>
+</pre></div>
+
+
+<p>If you prefer to start with an empty dataset you should use the <code>empty</code> parameter instead e.g.</p>
+<div class="codehilite"><pre><span class="n">jdbc</span><span class="o">:</span><span class="n">jena</span><span class="o">:</span><span class="n">men</span><span class="o">:</span><span class="n">empty</span><span class="o">=</span><span class="kc">true</span>
+</pre></div>
+
+
+<p>If both are specified then the <code>dataset</code> parameter has precedence.</p>
 <h3 id="tdb">TDB</h3>
+<p>The TDB driver provides access to a persistent <a href="/documentation/tdb/">Jena TDB</a> dataset.  This
+means that the dataset is both persistent and can be used transactionally.  For correct
+transactional behavior it is typically necessary to set the holdability for connections and 
+statements to <code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> as otherwise closing a result set or making
+an update will cause all other results to be closed.</p>
+<p>Beyond the common parameters the driver requires a single <code>location</code> parameter that provides
+the path to a location for a TDB dataset e.g.</p>
+<p>jdbc:jena:tdb:location=/path/to/data</p>
+<p>By default a TDB dataset will be created in that location if one does not exist, if you would
+prefer not to do this i.e. ensure you only access existing TDB datasets then you can add the
+<code>must-exist</code> parameter e.g.</p>
+<p>jdbc:jena:tab:location=/path/to/data&amp;must-exist=true</p>
+<p>With this parameter set the connection will fail if the location does not exist as a directory,
+note that this does not validate that the location is a TDB dataset so it is still possible
+to pass in invalid paths even with this set.</p>
 <h3 id="remote-endpoint">Remote Endpoint</h3>
   </div>
 </div>