xhrg opened a new issue #8430:
URL: https://github.com/apache/shardingsphere/issues/8430


   test conditions:::
   *  sharding-proxy-4.1.1
   *  mysql 5.7.30
   *  create the database name ssdb in MySQL for test
   
   ---
   
   testing procedure:::
   **config sharding-proxy**
   `schemaName: sharding_db
   dataSources:
     ds0: 
       url: jdbc:mysql://127.0.0.1:3306/ssdb?serverTimezone=UTC&useSSL=false
       username: root
       password: root
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 65
   shardingRule:
     tables:
       t_order:
         actualDataNodes: ds0.t_order_${0..1}
         databaseStrategy:
           inline:
             shardingColumn: order_id
             algorithmExpression: ds0
         tableStrategy: 
           inline:
             shardingColumn: order_id
             algorithmExpression: t_order_${order_id % 2}
         keyGenerator:
           type: SNOWFLAKE
           column: order_id
     bindingTables:
       - t_order
     defaultTableStrategy:
       none:`
   
   
   Abnormal situation::::
   case 1:The database name must be configured to use Navicat,if not,will 
error。(使用Navicat必须设置数据库名称,否则会失败)
   case 2:use mysql -u root -p,Log in MySQL,if you “show tables”,Incorrect 
display
   
   > use sharding_db
   > database changed
   > show tables;
   +----------------------+
   |   Tables_in_ssdb           |
   +----------------------+
   |  t_order                         |
   +----------------------+         Why is it shown here “Tables_in_ssdb”  is 
not  “Tables_in_sharding_db”
   
   case 3:when i use DataGrip,All configuration methods will not 
succeed(使用DataGrip,怎么配置都不会成功)
   
   
   
   
   


----------------------------------------------------------------
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]


Reply via email to