# Named query insert to table, column always null

**URL:** <https://forum.inductiveautomation.com/t/named-query-insert-to-table-column-always-null/100478>\
**Category:** Ignition\
**Created:** [January 6, 2025, 2:50pm UTC](https://forum.inductiveautomation.com/t/named-query-insert-to-table-column-always-null/100478 "2025-01-06T14:50:43Z")\
**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:** [January 6, 2025, 3:34pm UTC](https://forum.inductiveautomation.com/t/named-query-insert-to-table-column-always-null/100478/9 "2025-01-06T15:34:08Z")

</div>

I assumed the script still showed as running in the gateway status page for running scripts. If so, that's an infinite loop. If not, then your script has some problem you can't see, possibly because your try-catch clause cannot catch java exceptions.

> [@Issue passing selected row data to a pop-up](https://forum.inductiveautomation.com/t/issue-passing-selected-row-data-to-a-pop-up/99709/4):
>
> Python's Exception class doesn't include the panoply of java exceptions that can occur, particularly any SQLException that JDBC can throw. You should include another except Throwable, t: clause for those, where you include a from java.lang import Throwable above your try:. (Preferably in a project library script where you delegate your event and action scripts, so it can be imported as a persistent global.) Also, note that stringifying an exception loses the traceback, which is a real probl…

---

_[View the full topic](https://forum.inductiveautomation.com/t/named-query-insert-to-table-column-always-null/100478)._