[
https://issues.apache.org/jira/browse/JENA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966023#comment-13966023
]
ASF subversion and git services commented on JENA-673:
------------------------------------------------------
Commit 1586511 from [email protected] in branch 'jena/trunk'
[ https://svn.apache.org/r1586511 ]
Infrastructure to allow setting JDBC compatibility level on a per-query basic
(JENA-673)
> 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
>
> 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)
