# SQL getKey Returning Wrong Column

**URL:** <https://forum.inductiveautomation.com/t/sql-getkey-returning-wrong-column/69795>\
**Category:** Ignition\
**Tags:** ignition80, database, scripting, ignition81\
**Created:** [February 13, 2023, 9:37pm UTC](https://forum.inductiveautomation.com/t/sql-getkey-returning-wrong-column/69795 "2023-02-13T21:37:48Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [February 12, 2024, 7:52pm UTC](https://forum.inductiveautomation.com/t/sql-getkey-returning-wrong-column/69795/8 "2024-02-12T19:52:37Z")

</div>

The true result set from a JDBC driver's `getGeneratedKeys()` implementation is now available via `system.db.runPrepInsert()`. (Yeah, no, not built into Ignition.)

> [@Automation Professionals' Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/89):
>
> Automation Professionals is pleased to announce a new release of the Integration Toolkit module. This release adds one new scripting function, [system.db.runPrepInsert()](https://www.automation-pros.com/toolkit/doc/utility.html#runprepinsert). It is very similar to IA's [system.db.runPrepUpdate()](https://docs.inductiveautomation.com/display/DOC81/system.db.runPrepUpdate), intepreting the query, args, database, and tx arguments in the same fashion. The getKey argument is omitted as moot, as this function always retrieves generated keys. The skipAudit optional argument is unimplemented. For Ignition v8.1+: [v2.0.15.240431913](https://www.automation-pros.com/ignition/Integration%20Toolkit-2.0.15.240431913-v81.modl) Do note the docu…

---

_[View the full topic](https://forum.inductiveautomation.com/t/sql-getkey-returning-wrong-column/69795)._