Uh oh!
There was an error while loading. Please reload this page.
feat: expose lossless MySQL user variables - #55
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Why
ProxySQL currently falls back to hostgroup locking for client statements such as:
The downstream consumer needs typed assignments and the exact literal spelling before it can safely track and replay these values. Reconstructing that information from normalized SQL would lose literal semantics, so ParserSQL is the source of truth.
Details
NULLliteral nodes+/-signs for numeric literalsValidation
make test: 1,333 tests run; 1,296 passed; 37 backend-dependent tests skippedmake build-corpus-test: passedDownstream
Companion ProxySQL PR: sysown/proxysql#6043
That PR vendors the archive produced from commit
db9d464c334eaba236bea16a6e9eb6efa7c3a863and uses these typed results for bounded user-variable tracking and backend replay.