# Transactional Group Records Getting Stuck In Store & Forward

**URL:** <https://forum.inductiveautomation.com/t/transactional-group-records-getting-stuck-in-store-forward/110708>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [September 17, 2025, 12:24pm UTC](https://forum.inductiveautomation.com/t/transactional-group-records-getting-stuck-in-store-forward/110708 "2025-09-17T12:24:36Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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 22, 2025, 8:21pm UTC](https://forum.inductiveautomation.com/t/transactional-group-records-getting-stuck-in-store-forward/110708/9 "2025-09-22T20:21:58Z")

</div>

Consider switching to a DB brand that:

1. Supports the SQL standard `ON CONFLICT` clause, or similar non-standard functions (aka UPSERT).

2. Supports arrays in JDBC and the SQL standard `UNNEST` function to convert arrays to table-like objects.

( \* _Cough_ \* _PostgreSQL_ \* _Cough_ \* )

> [@Taking a Dataset and Inserting it to a SQL temp table](https://forum.inductiveautomation.com/t/taking-a-dataset-and-inserting-it-to-a-sql-temp-table/83852/4):
>
> If you were using a competent database (the following is PostgreSQL), you can pass java arrays as arguments, and unnest() them in a FROM clause. For an example, I created a table in my psql forum playground called phrases, to be used in a join. When queried by itself, you get this dataset: "#NAMES" "prefix","suffix" "#TYPES" "str","I" "#ROWS","4" "Hello","1" "Good Bye","2" "Welcome to","3" "Whoa!","4" To go with that, in a custom property named lookups, I created the following unbound datase…

---

_[View the full topic](https://forum.inductiveautomation.com/t/transactional-group-records-getting-stuck-in-store-forward/110708)._