fix: return error to client if prepare stmt param not match #2918
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
before: (in server)
2023-12-12T11:39:05.369596Z WARN servers::mysql::server: Internal error occurred during query exec, server actively close the channel to let client try next time err=0: Expected type: Timestamp(Millisecond(TimestampMillisecondType)), actual: MYSQL_TYPE_VAR_STRING, at src/servers/src/mysql/helper.rs:168:14
after: (in client)
com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: err: Expected type: Timestamp(Millisecond(TimestampMillisecondType)), actual: MYSQL_TYPE_VAR_STRING, params: (Value(Bytes([49])), MYSQL_TYPE_VAR_STRING),(Value(Int(1)), MYSQL_TYPE_LONG),(Value(Int(1)), MYSQL_TYPE_LONG),(Value(Int(1)), MYSQL_TYPE_LONG),(Value(Int(1)), MYSQL_TYPE_LONG),(Value(Int(1)), MYSQL_TYPE_LONG),(Value(Int(1)), MYSQL_TYPE_LONG)
Checklist
Refer to a related PR or issue link (optional)