You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by rv...@apache.org on 2013/04/04 01:38:34 UTC
svn commit: r1464237 - /jena/Experimental/jena-jdbc/README
Author: rvesse
Date: Wed Apr 3 23:38:34 2013
New Revision: 1464237
URL: http://svn.apache.org/r1464237
Log:
Update README with an up to date to do list
Modified:
jena/Experimental/jena-jdbc/README
Modified: jena/Experimental/jena-jdbc/README
URL: http://svn.apache.org/viewvc/jena/Experimental/jena-jdbc/README?rev=1464237&r1=1464236&r2=1464237&view=diff
==============================================================================
--- jena/Experimental/jena-jdbc/README (original)
+++ jena/Experimental/jena-jdbc/README Wed Apr 3 23:38:34 2013
@@ -51,6 +51,9 @@ empty=true
Sets that the driver will run against an initially empty dataset
+Notes:
+- In-Memory datasets do not support transactions
+
TDB
---
@@ -66,6 +69,10 @@ must-exist=true
If set then ensures that only existing TDB datasets may be used, prevents incorrect paths leading to unexpected empty datasets
+Notes:
+- TDB is always used in transactional mode, auto-commit is on by default
+- Using the in-memory dataset is NOT recommended for anything other than unit testing
+
Remote
------
@@ -81,6 +88,9 @@ update=http://example.org/update
Sets the SPARQL Update endpoint to use, one/both of this and the query parameter must be set. Set only this for a write-only connection
+Notes:
+- Remote connections do not support transactions
+
To Do List
==========
@@ -90,9 +100,16 @@ This is early experimental prototyping a
- JDBC Compatibility
- Provide a compatibility level parameter for all drivers that configures some aspects of behaviour depending on how JDBC like the
user needs a connection to be
+ e.g. currently we report column types as strings so that data is usable with generic JDBC apps, it may be better to allow this to
+ be configured so applications that talk SPARQL can have columns typed as Node
- Connections
- - Support transactions for Dataset backed connections
- - Flesh out proper support for database metadata
-- Query and Result Handling
+ - Flesh out proper support for database metadata, needs lots of reporting of various metadata that we don't yet provide
+- Drivers
+ - Support auto-commit parameter for TDB driver URLs
+ - Support default-graph-uri (and so forth) parameters for Remote Endpoint driver URLs
+ - Support authentication parameters for Remote Endpoint driver URLs
+ - Provide a convenience Fuseki Driver which is merely a layer over a Remote Endpoint driver
+- Statement and Result Handling
- Implement a ResultSetBuffered to support setFetchSize()
- - Implement variants of the result sets classes in order to support FETCH_FORWARD_REVERSE
+ - Implement variants of the result sets classes in order to support TYPE_SCROLL_INSENSITIVE
+ - Support PreparedStatement