[
https://issues.apache.org/jira/browse/IGNITE-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-8164:
-----------------------------------
Description:
Since we've implemented a transactional SQL, we need to reflect it in our JDBC
driver. At the moment our implementation of {{java.sql.DatabaseMetaData}}
returns incorrect data. For example, methods
{{boolean supportsTransactions()}}
and
{{boolean supportsTransactionIsolationLevel(int level)}}
return hardcoded \{{false}} value, which is incorrect if MVCC is enabled. We
need to fix it.
was:
Since we've implemented a transactional SQL, we need to reflect it in our JDBC
driver. At the moment our implementation of {{java.sql.DatabaseMetaData}}
returns incorrect data. For example, methods
{{boolean supportsTransactions()}}
and
{{boolean supportsTransactionIsolationLevel(int level)}}
return hardcoded {{false }}value, which is incorrect if MVCC is enabled. We
need to fix it.
> SQL TX: JDBC driver meta data update.
> -------------------------------------
>
> Key: IGNITE-8164
> URL: https://issues.apache.org/jira/browse/IGNITE-8164
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
> Reporter: Roman Kondakov
> Priority: Major
> Labels: iep-3
>
> Since we've implemented a transactional SQL, we need to reflect it in our
> JDBC driver. At the moment our implementation of
> {{java.sql.DatabaseMetaData}} returns incorrect data. For example, methods
> {{boolean supportsTransactions()}}
> and
> {{boolean supportsTransactionIsolationLevel(int level)}}
> return hardcoded \{{false}} value, which is incorrect if MVCC is enabled. We
> need to fix it.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
