# Postgresql V10 Transaction Group creates INT not BOOL

**URL:** <https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112>\
**Category:** Ignition\
**Tags:** ignition79, database\
**Created:** [October 12, 2018, 1:59am UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112 "2018-10-12T01:59:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![0sm0](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/0sm0/32/15228_2.png) [@0sm0](https://forum.inductiveautomation.com/u/0sm0)\
**Post date:** [October 12, 2018, 1:59am UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112/1 "2018-10-12T01:59:41Z")

</div>

Hi guys,

Ignition V7.9.9  
windows 10  
postgresql v10.5

Using a Historical Transaction Group, a new group has a Boolean Data type column, when the postrgesql table is created the column has an Integer datatype instead. This then leads to errors etc…

Changing the integer datatype to boolean in DB or the boolean to interger in the TG allows for the transaction to work ok. Its just the initial creation that makes a boolean an integer.

I have used postgresql in the past and never seemed to have this issue?

Any ideas appreciated

Cheers

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 12, 2018, 12:10pm UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112/2 "2018-10-12T12:10:15Z")

</div>

That’s just Ignition trying to play to the least common denominator among supported databases. In other words, some popular databases don’t really have a true boolean datatype, where a tinyint is used instead. Not that it shouldn’t be addressed, but it isn’t a surprise.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 12, 2018, 3:23pm UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112/3 "2018-10-12T15:23:59Z")

</div>

If you want to, you can change the Postgres ‘translator’ settings to use a different default column type for boolean values - go to Configure → Databases → Drivers, then translators along the top, and then you can change the data type mapping for the Postgres translator:

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

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 12, 2018, 4:38pm UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112/4 "2018-10-12T16:38:39Z")

</div>

> [@paul-griffith](#):
>
> can change the data type mapping for the Postgres translator

Huh. Never noticed that one.

---

<div class="post-metadata">

**Author:** ![0sm0](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/0sm0/32/15228_2.png) [@0sm0](https://forum.inductiveautomation.com/u/0sm0)\
**Post date:** [October 13, 2018, 1:24am UTC](https://forum.inductiveautomation.com/t/postgresql-v10-transaction-group-creates-int-not-bool/20112/5 "2018-10-13T01:24:48Z")

</div>

Haha, well there you go…

I should learn to scroll down further in future… 🙂

Will give it ago

Many thanks.