# JDBC and AutoCommit

**URL:** <https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241>\
**Category:** Ignition\
**Created:** [September 19, 2022, 6:32pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241 "2022-09-19T18:32:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marioishikawa](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marioishikawa/32/7352_2.png) [@marioishikawa](https://forum.inductiveautomation.com/u/marioishikawa)\
**Post date:** [September 19, 2022, 6:32pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241/1 "2022-09-19T18:32:01Z")

</div>

I’m using the JDBC connector for a different Database but I’m having a problem when writing to the database using the SQL Bridge for a Historical Group. The JDBC is trying to set AutoCommit, which apparently is an optional function that is not supported by the JDBC driver (Simba for BigQuery). Is there any way to disable this?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 19, 2022, 6:58pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241/2 "2022-09-19T18:58:18Z")

</div>

Unfortunately no, setAutoCommit is called all over the code base, with `true` or `false`, depending on the context, with no notion that it might not be supported. That’s the first I’ve ever heard such a thing.

---

<div class="post-metadata">

**Author:** ![marioishikawa](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marioishikawa/32/7352_2.png) [@marioishikawa](https://forum.inductiveautomation.com/u/marioishikawa)\
**Post date:** [September 19, 2022, 7:21pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241/3 "2022-09-19T19:21:46Z")

</div>

Thanks. It has been hard to do this connection with BigQuery. It does not have transactions, as well PK and indexes. I could manage the index adding “Select 1” on the translator for index creation and it went through. Do you imagine any workaround like that I could use?

---

<div class="post-metadata">

**Author:** ![calimero100582](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/calimero100582/32/18630_2.png) [@calimero100582](https://forum.inductiveautomation.com/u/calimero100582)\
**Post date:** [September 19, 2022, 7:41pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241/4 "2022-09-19T19:41:41Z")

</div>

was curious about this one

are you able to set IgnoreTransactions flag. It seems to be a solution for ODBC that, I hope, should also work with JDBC

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/2/520e477db0cd549f071f222dc3bc6b6dbf7a07a5.png)

---

<div class="post-metadata">

**Author:** ![marioishikawa](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marioishikawa/32/7352_2.png) [@marioishikawa](https://forum.inductiveautomation.com/u/marioishikawa)\
**Post date:** [September 19, 2022, 7:55pm UTC](https://forum.inductiveautomation.com/t/jdbc-and-autocommit/64241/5 "2022-09-19T19:55:07Z")

</div>

Beautiful! It worked like a charm! Thank you very much! I was trying so many paramaters names to reach something like this! LOL

EnableSession=0;EnableTransaction=false;autocommit=FALSE;setautocommit=false;setautocommit=0;IgnoreTransactions=1;