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
Currently, the template INSERT INTO table (a, b) VALUES (?, UNIX_TIMESTAMP(?)) fails in formatError with the message "foo". Obviously, the regex used in formatError can't match the the '?' characters in templates like the one given above.
My suggestion is to perform substition more closely oriented to '?'-characters, und thus make the template more permissive by allowing SQL expressions inside.
Maybe, #12 could be addressed simultaneously, if a method other than regex matching is chosen for checking the template's well- or ill-formedness / splitting the query into template and non-template parts.
NB. buildQuery, which performs the actual substitution of the '?' characters, seems permissive enough at first glance...
The text was updated successfully, but these errors were encountered:
I'd be willing to implement and send you a PR; I'd just need to know if this feature is desired at all, the way I proposed it, or if it doesn't fit the concept somehow.
Currently, the template
INSERT INTO table (a, b) VALUES (?, UNIX_TIMESTAMP(?))
fails in formatError with the message "foo". Obviously, the regex used in formatError can't match the the '?' characters in templates like the one given above.My suggestion is to perform substition more closely oriented to '?'-characters, und thus make the template more permissive by allowing SQL expressions inside.
Maybe, #12 could be addressed simultaneously, if a method other than regex matching is chosen for checking the template's well- or ill-formedness / splitting the query into template and non-template parts.
NB. buildQuery, which performs the actual substitution of the '?' characters, seems permissive enough at first glance...
The text was updated successfully, but these errors were encountered: