It turns out that this was caused by the client itself NOT the SQL syntax.

Apparently DBeaver was the culprit. If anyone experiences this issue with DBeaver, there is an option to turn off variables.