tsh proxy db messes with NodeJs mariadb driver on JSON columns

[Tchekda]

Expected behavior:

When connecting a NodeJS app to a remote MariaDB 11.4.4 via tsh proxy db, I am expecting to have the same functionality as if I were connecting locally to that same database.

Current behavior:

Currently, when connecting via tsh proxy db, the app is crashing on some MariaDB specific calls like JSON columns. The fix is to use mysql driver to have some compatibility on some features but not all of them.

Running this same app directly on the MariaDB server works perfectly fine with the mariadb driver.

This is why we concluded the tsh proxy db was faulty and wasn't fully compatible with MariaDB operations.

Bug details:

• Teleport version:

Teleport v16.4.6 git: go1.22.10
Proxy version: 17.2.2

• Recreation steps
  • Build a NodeJS app that connects to a MariaDB server and leverages JSON columns (via an ORM like sequelize)
  • See the output difference of a direct connection and a proxied one. In the first one the JSON is parsed correctly but in the second the JSON is returned as string
• Debug logs
  • No logs found