# Weird MySQL errors

**URL:** <https://forum.inductiveautomation.com/t/weird-mysql-errors/19025>\
**Category:** Ignition\
**Created:** [July 31, 2018, 2:23am UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025 "2018-07-31T02:23:09Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 31, 2018, 2:23am UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/1 "2018-07-31T02:23:09Z")

</div>

Keeping getting this almost generic like error on windows where a MySQL query is used to populate a text field or display data, Running diagnostic on screen shows not errors, and there are no error overlays on any of the screens, just this annoying error popup:

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

Different screen, but same ‘generic’ error:

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/746798fc01805f66451adfdaaf5341a85ac84dad.png)

MySQL server V5.7

Ignition V7.9.8

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/8/86a61e01b0413277eaa48efd91fef09f3a27c028.png)

---

<div class="post-metadata">

**Author:** ![jonathan.taylor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jonathan.taylor/32/4048_2.png) [@jonathan.taylor](https://forum.inductiveautomation.com/u/jonathan.taylor)\
**Post date:** [July 31, 2018, 1:58pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/2 "2018-07-31T13:58:20Z")

</div>

What does the full error message say, rather than the compact?

---

<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:** [July 31, 2018, 3:17pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/3 "2018-07-31T15:17:47Z")

</div>

This is related to an issue that’s been documented elsewhere on the forum - but basically, while you’re on 7.9.8 you’ll have to go into any query bindings and make sure that the ‘Update Query’ field (if it’s there) is both empty and disabled before saving the binding.  
The behavior of these bindings is fixed in 7.9.9.

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 31, 2018, 3:28pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/4 "2018-07-31T15:28:31Z")

</div>

[full error.txt](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/30a89ec577720bf741b5a239fa7d92725f1d06ef.txt) (5.3 KB)

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 31, 2018, 3:29pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/5 "2018-07-31T15:29:58Z")

</div>

When is 7.9.9 scheduled to be released?  
This is on a brand new install and it does not go over well the the end customer.

---

<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:** [July 31, 2018, 3:55pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/6 "2018-07-31T15:55:37Z")

</div>

> [@Curlyandshemp](#):
>
> When is 7.9.9 scheduled to be released?

Soon; i.e., within weeks.

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [July 31, 2018, 7:23pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/7 "2018-07-31T19:23:08Z")

</div>

This is the culprit. Now i have to hunt each component on all the screens and shut these off:

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/51736a79c0f6a32a03317ee8a1393a5f86ab3deb.png)

---

<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:** [July 31, 2018, 7:35pm UTC](https://forum.inductiveautomation.com/t/weird-mysql-errors/19025/8 "2018-07-31T19:35:52Z")

</div>

Yep - that’s the issue. Note that this should only affect modified or newly created bindings since 7.9.7 - bindings that haven’t changed since before 7.9.7 should still work fine. As I mentioned before - in order to manually fix them you’ll have to empty out the update query entirely, then disable, then ok the binding change.