You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/A query with a comment containing a ? will have it replaced/ instead of the ? in the real query.
I suppose I could just put the comment in js instead of the query string, but it's pretty large and multi-line
using these
escapes
so I could area-select the query and test it straight in the mysql client, so the comment inline seems appropriate.
If not worth addressing, maybe just a "do not put ? in /query comments/ " in the documentation would clarify.
Otherwise, wonderfully useful driver!
The text was updated successfully, but these errors were encountered:
Thanks, this is definitely not something we are going to fix and is simply a limitation of the ?-replacement stuff. I'll add a note about this limitation to the documentation. For reference, we simply blindly swap instances of ? for the values, otherwise we would need a full SQL language parser, which just adds complexity and is slower.
/A query with a comment containing a ? will have it replaced/ instead of the ? in the real query.
I suppose I could just put the comment in js instead of the query string, but it's pretty large and multi-line
using these
escapes
so I could area-select the query and test it straight in the mysql client, so the comment inline seems appropriate.
If not worth addressing, maybe just a "do not put ? in /query comments/ " in the documentation would clarify.
Otherwise, wonderfully useful driver!
The text was updated successfully, but these errors were encountered: