56 cases of mysql_client_test
failed
#44672
Labels
type/enhancement
The issue or PR belongs to an enhancement.
mysql_client_test
failed
#44672
Bug Report
0. Background
mysql_client_test
is the test cases in mysql repository. It's used to test both the server and the client(libmysql) implementation. As a MySQL-compatible database, I think it'd be better to pass all these tests. It can enrich our test cases on protocol layer.Unfortunately, tons of the test cases have failed. They can be concluded in the following areas (except known unsupported features):
ComFieldList
. The type and length of a field is usually different from the expectation of the tests. I'm not sure whether it's expected.1. Minimal reproduce step (Required)
git clone https://github.com/YangKeao/mysql-server.git -b known-bugs
testclients/mysql_client_test.cc
, and find "TODO" in it. Several lines are commented out with "TODO: need fix", which means this test case cannot pass on TiDB.mysql_client_test
. Assume the location ofmysql_client_test
binary is at./cmake-build-mysql/runtime_output_directory/mysql_client_test
MYSQL_TEST_DIR=$(pwd)/mysql-test ./cmake-build-mysql/runtime_output_directory/mysql_client_test -P 4000 -h 127.0.0.1 -u root
, you'll see the error output.For example, if I uncommented
test_func_fields
, I'll get:2. What did you expect to see? (Required)
All tests passed (except those which are known to be unsupported, like procedure, unsupported character set (utf8mb3) and other features).
3. What did you see instead (Required)
A lot of tests failed.
org_name
for expression #45145MYSQL_TIMESTAMP_DATETIME_TZ
#45144test_bug33781442Don't need to fix. Because TiDB and MySQL returns the aggregation of BIT columns in different format (TiDB in Binary, and MySQL in text). Both are fine for a standard client. See https://bugs.mysql.com/bug.php?id=67225SET @@timestamp=UNIX_TIMESTAMP
does not take effect in TiDB #31648SET @@timestamp=UNIX_TIMESTAMP
does not take effect in TiDB #31648SET @@timestamp=UNIX_TIMESTAMP
does not take effect in TiDB #31648SET @@timestamp=UNIX_TIMESTAMP
does not take effect in TiDB #31648show ...
statement should setorg_name
for every columns #464024. What is your TiDB version? (Required)
0013190
The text was updated successfully, but these errors were encountered: