# Transaction group millisecond

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795>\
**Category:** Ignition\
**Created:** [September 17, 2020, 1:30pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795 "2020-09-17T13:30:09Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![MoisesZV](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@MoisesZV](https://forum.inductiveautomation.com/u/MoisesZV)\
**Post date:** [September 17, 2020, 1:30pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/1 "2020-09-17T13:30:09Z")

</div>

Hi, I have a historical group that is set to save data every 250ms to a mysql database. This is being achieved but when calling the data to an easy chart I can see that the four records that make up a second are displayed all together in the same second and not spaced by milliseconds. Is this a transactional group problem? or what would be the problem?

---

<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:** [September 17, 2020, 2:41pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/2 "2020-09-17T14:41:49Z")

</div>

That usually means your DB isn’t saving the milliseconds. For PostgreSQL, you’d specify the column type as timestamptz(3) for milliseconds, timestamptz(6) for microseconds, timestamptz(0) for seconds. PostgreSQL defaults to (6). It is similar for MariaDB and datetime columns, but the default is (0). I’m not sure what you’d use for MySQL (why are you using MySQL?).

---

<div class="post-metadata">

**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\
**Post date:** [September 17, 2020, 2:47pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/3 "2020-09-17T14:47:08Z")

</div>

> [@pturmel](#):
>
> MySQL (why are you using MySQL?).

Forget the dolphin. Move on to the Sea Lion (MariaDB).

---

<div class="post-metadata">

**Author:** ![MoisesZV](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@MoisesZV](https://forum.inductiveautomation.com/u/MoisesZV)\
**Post date:** [September 17, 2020, 5:14pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/4 "2020-09-17T17:14:08Z")

</div>

Now I using MariaDB, I set DATETIME (6) to t\_stamp but the Transaction group don’t save millisecond.

```auto
CREATE TABLE IF NOT EXISTS `test_rapido` (
  `test_rapido_ndx` int(11) NOT NULL AUTO_INCREMENT,
  `t_stamp` DATETIME (6),
  `M400_3` int(11) DEFAULT NULL,
  `M400_4` int(11) DEFAULT NULL,
  PRIMARY KEY (`test_rapido_ndx`),
  KEY `test_rapidot_stampndx` (`t_stamp`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=latin1;

```

 ![mariadb](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/3/e331dc8c38f125fc0388cce1f2da2cf92983b9f5.jpeg)

---

<div class="post-metadata">

**Author:** ![MoisesZV](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@MoisesZV](https://forum.inductiveautomation.com/u/MoisesZV)\
**Post date:** [September 17, 2020, 5:25pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/5 "2020-09-17T17:25:41Z")

</div>

I think that using transactional groups it is not possible to save milliseconds but it is possible using the tag historian module.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [September 17, 2020, 5:27pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/6 "2020-09-17T17:27:48Z")

</div>

It is possible, try using a timestamp column.

---

<div class="post-metadata">

**Author:** ![MoisesZV](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@MoisesZV](https://forum.inductiveautomation.com/u/MoisesZV)\
**Post date:** [September 17, 2020, 6:10pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/7 "2020-09-17T18:10:39Z")

</div>

I set de datatype to TIMESTAMP but the transaction group still don’t save milliseconds

 ![maridbconfig](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/d/fd656fd1071c1f619aba1a71f0f4d867532cb7d5.jpeg)  
 ![data maria](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/6/76cb9ab495de0aa5bce59f66f6909176d250718e.jpeg)

---

<div class="post-metadata">

**Author:** ![MoisesZV](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@MoisesZV](https://forum.inductiveautomation.com/u/MoisesZV)\
**Post date:** [September 22, 2020, 8:13pm UTC](https://forum.inductiveautomation.com/t/transaction-group-millisecond/38795/8 "2020-09-22T20:13:06Z")

</div>

Using TIMESTAMP(6) with mysql did the job, thanks for the advice.