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
I've ran into an issue where my legacy tables use mysql reserved words (in my case, "to") as column names, and the autocomplete plugin fails to fetch the data due to a MySQL error.
To fix this, I added "quote_column_name()" calls around the "method" variables in the "auto_complete_for" method:
Using ? would transform it into a string, like: 'column_name' (see the difference between grave accents and single quotes), to which MySQL would treat as a literal value and not a column, as opposed to column_name.
(edit: this comment system parses grave accents into code, but I hope you get the idea.)
I've ran into an issue where my legacy tables use mysql reserved words (in my case, "to") as column names, and the autocomplete plugin fails to fetch the data due to a MySQL error.
To fix this, I added "quote_column_name()" calls around the "method" variables in the "auto_complete_for" method:
I'm not sure this is an elegant solution though.
The text was updated successfully, but these errors were encountered: