Problem with colon in a table or column name (enclosed by back ticks) #40
Description
I can't seem to get around an issue where my database schema require some tables to have colons in the table name. This creates an issue when the query is executed as the parser treats the colon (even though its not preceded by a space character) in the middle of the table name as the start of an expectant named parameter that does not exist.
Proposed solution:
The parser should only consider placeholders that are preceded by a space or that is NOT enclosed in back ticks (representing a table or column name).
Any chance this can be fixed please?