strongduanmu commented on issue #7918:
URL: https://github.com/apache/shardingsphere/issues/7918#issuecomment-718808156
## DCL Statements
@lwtdev I have checked the MySQL documentation again and found that the
definition of the `SET PASSWORD` statement has changed in version 8.0, and
version 5.7 supports PASSWORD systax.
```sql
SET PASSWORD [FOR user] = password_option
password_option: {
'auth_string'
| PASSWORD('auth_string')
}
```
I think we should support these two different versions of the syntax at the
same time.
## DAL Satements
> Maybe we can support show create ? when we support create ? . I found that
there are already some issues related to this.
Thank you very much for your suggestions. We will check similar syntax
combinations later and support these SQLs as soon as possible.
> ShardingProxy(5.0.0.RC1)No Sharding
showKeysWithLike[hasShardingKey:none]; Support:false; SQL: SHOW KEYS
in customer in db1 where column_name like '%id%';
java.sql.SQLException: 2Unknown exception: [Conversion = 'i']
This is caused by a sql parse error and will be fixed in this PR.
## RL Statements
> ShardingProxy(5.0.0.RC1)No Sharding
startSlaveIoThread[hasShardingKey:none]; Support:false; SQL: start
slave io_thread until RELAY_LOG_FILE = 'log_name', RELAY_LOG_POS = 4;
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: This version of
ShardingProxy doesn't yet support this SQL. 'Unsupported SQL of `start slave
io_thread until RELAY_LOG_FILE = 'log_name', RELAY_LOG_POS = 4`'
This SQL will be supported after PR is merged.
Thank you very much for the various test cases you have been providing. This
is very important for the improvement of the SS 5.X version.
In order to facilitate the quick communication and resolution of follow-up
questions, would you mind sending your WeChat account to my
e-mail——[email protected]?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
