# Outstanding queries after upgrade to 4.4.5

**URL:** <https://forum.mautic.org/t/outstanding-queries-after-upgrade-to-4-4-5/26884>\
**Category:** Mautic 4 Install/Upgrade Support\
**Created:** [January 27, 2023, 7:27pm UTC](https://forum.mautic.org/t/outstanding-queries-after-upgrade-to-4-4-5/26884 "2023-01-27T19:27:38Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![fkrafft](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/fkrafft/32/2220_2.png) [@fkrafft](https://forum.mautic.org/u/fkrafft)\
**Post date:** [January 19, 2025, 10:55pm UTC](https://forum.mautic.org/t/outstanding-queries-after-upgrade-to-4-4-5/26884/8 "2025-01-19T22:55:44Z")

</div>

Any update on the “right way” to handle these table references?

And FYI, I have similar problem on a 4.4.13.  
I checked that the  
_client\_id_ in _oauth2\_user\_client\_xref_ matched  
the _id_ in _oauth2\_clients._

And they are of the same type and length.

DESCRIBE oauth2\_clients;  
±--------------------±-----------------±-----±----±--------±---------------+  
| Field | Type | Null | Key | Default | Extra |  
±--------------------±-----------------±-----±----±--------±---------------+  
| id | int(10) unsigned | NO | PRI | NULL | auto\_increment |

DESCRIBE oauth2\_user\_client\_xref;  
±----------±-----------------±-----±----±--------±------+  
| Field | Type | Null | Key | Default | Extra |  
±----------±-----------------±-----±----±--------±------+  
| client\_id | int(10) unsigned | NO | PRI | NULL | |

---

_[View the full topic](https://forum.mautic.org/t/outstanding-queries-after-upgrade-to-4-4-5/26884)._