You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2014/05/28 11:49:04 UTC
[jira] [Closed] (JENA-673) Allow JDBC compatibility level to be set
on a per-query basis
[ https://issues.apache.org/jira/browse/JENA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Vesse closed JENA-673.
--------------------------
Resolution: Fixed
Fix Version/s: Jena 2.11.2
Closing with correct Fix Version applied
> Allow JDBC compatibility level to be set on a per-query basis
> -------------------------------------------------------------
>
> Key: JENA-673
> URL: https://issues.apache.org/jira/browse/JENA-673
> Project: Apache Jena
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: Jena 2.11.1
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Minor
> Fix For: Jena 2.11.2
>
>
> At the ApacheCon talk today the question was raised of why we made JDBC compatibility a connection level setting and not a per-query setting.
> It makes sense to support both modes and should in principal be a relatively easy improvement to make.
--
This message was sent by Atlassian JIRA
(v6.2#6252)