MySql dialect doesn't handle slash-escaped single quotes

[WesleyAC]

The following fails to parse:

fn main() {
    println!("{:?}",
        sqlparser::parser::Parser::parse_sql(
            &sqlparser::dialect::MySqlDialect {},
            r#"INSERT INTO `example` (`col`) VALUES ('foo \'bar\' baz');"#
        )
    );
}

Instead returning:

Err(ParserError("Expected ), found: bar"))

But I believe it shouldn't — mysqldump generates SQL that is escaped like this, and the docs explicitly mention this as a valid escaping (see Table 9.1).

This is, according to this doc a difference between ANSI SQL and MySQL, but unfortunately this needs to be fixed in the tokenizer, which AFAICT the dialect system doesn't have a way to hook into?

[houqp]

looks like a bug to me and I think you are right that the current dialect trait needs to be extended to support this use-case.

[sanxiyn]

This seems fixed. If so, please close.