lideming

> how results from the db are being processed It's what their generated JS code do, which read and parse result rows from the db.

It should work without additional configuration on the client. But there may be some problem for some MySQL server configuration as we didn't implement the [Authentication Method Mismatch](https://dev.mysql.com/doc/dev/mysql-server/8.0.12/page_protocol_connection_phase.html#sect_protocol_connection_phase_auth_method_mismatch) protocol.

Same, also on Arch Linux, when I was trying to convert a Windows 10 OS drive. Just searched in source and found the line that throws that error: https://github.com/maharmstone/ntfs2btrfs/blob/171e9b92114ca08207afc34ccb190b4a9dfd90fb/src/ntfs.cpp#L75

Should be fixed by #137 and #68.

It is intended. `new Client().connect()` does not create the connection but the connection pool.

Should be fixed by #137. Please reopen this issue if the problem still occurs.

@mrl5 The docs site is outdated. It was supported. I guess recent changes broke it😢. Trying fixing...

Can't reproduce the problem. Close it for now.

@shiyuhang0 It's the "Authentication Method Mismatch" part in Connection Phase (https://dev.mysql.com/doc/dev/mysql-server/latest/page_protocol_connection_phase.html). We have implemented only the "Authentication Phase Fast Path" currently and can not switch authentication method in case of...

Seems to be the ANSI_QUOTES mode (MySQL docs: https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_ansi_quotes). Currently the sql-builder module uses double quotes `"` for string values. (issue: https://github.com/manyuanrong/sql-builder/issues/15)