Its own repo: https://github.com/afs/jena-rdfconnection/

+ Examples. Documentation.

+ Whole datasets operations to complement graph store protocol operations.

+ Multi operation transactions, with implicit autocommit if not inside an explicit transaction.

+ Java8 style working. Instead of JDBC-style statement objects, I think we should encourage a style working where nesting issues don't lead to traps (e.g. transaction begin/end mismatches). There is already jena-jdbc for where there is a need for JDBC.

This also helps with the issues around creating a statement and passing it across transaction (and connection) boundaries.

That's not to say that JDBC Statement styles can't be achieved. Low-level basic operations for query and update are provided (they forn the the required implementations - RDFConnection provides default methods for Java8 style.) However, they are just not required to be used by applications. They can be written using java8 closures.

We could have separate library and implementation interface - at the moment RDFConnection is both by using default methods - but it's worth exploring the different styles that result.

        Andy

Reply via email to