Backtick around column names messes the parser around #5
Description
im using something like
`is_staff` = 1 OR `is_team` = 1 OR `is_department` = 1 OR `is_category` = 1
im passing the backticks in the id for the rules already
{
"id":"`is_team`",
"...."
}
the sql parser doesnt seem to be able to pick up the columns from the given sql vs the "rule" items. so it comes up blank.
im guessing theres a strip strange marks on the field names?
right now its an either or. either i pass the sql as above and leave the field names (id) without the backticks and it works but outputs sql without the backticks around column names.. or i break the loading up of sql (pre populating) with backticks and fieldnames with backticks but it then "outputs" sql with backticks.
so either, given that the stored sql is:
`is_team` = 1
using:
{
"id":"is_team",
"...."
}
the querybuilder rules works fine but it outputs the sql as:
is_team = 1
OR
i use
{
"id":"`is_team`",
"...."
}
and the query builder (sql parser) breaks cause it cant find the fields in the rules
but it outputs - when adding a new rule -
`is_team` = 1
which is what i want
might be useful for it to 1 to 1 match on the id value without stripping anything out if you use different tables n stuff.
{
"id":"`table`.`column`",
"...."
}