[GitHub] [shardingsphere] duanzonglong edited a comment on issue #6759: SHOW FULL COLUMNS get wrong

Thu, 24 Sep 2020 00:54:40 -0700 


duanzonglong edited a comment on issue #6759:
URL: https://github.com/apache/shardingsphere/issues/6759#issuecomment-697070898


   config-wms.yaml:
   
   schemaName: sharding_wms
   
   dataSources:
     wms_base:
     wms_sd0:
     wms_sd1:
     wms_sd2:
   
   shardingRule:
     defaultDatabaseStrategy:
       standard:
         shardingColumn: tenant_id
         preciseAlgorithmClassName: 
com.hrsoft.sharding.strategy.core.DatabaseStrategy
     defaultDataSourceName: wms_base
     tables:
       ds_changelog:
         actualDataNodes: wms_base. databasechangelog
         databaseStrategy:
           none:
         tableStrategy:
           none:
       ds_changelog_lock:
         actualDataNodes: wms_base. databasechangeloglock
         databaseStrategy:
           none:
         tableStrategy:
           none:
      more....
     bindingTables:
       - xxxxx
     defaultTableStrategy:
       none:  
   
   the framework is liquibase-3.9.0 with shardingproxy;
   if we don't use shardingproxy the liquibase is ok.
   
   the actual sql is:
   SHOW FULL COLUMNS FROM databasechangelog FROM sharding_wms LIKE '%'
   it's create by mysql-connector-java-8.0.20.jar
   
![image](https://user-images.githubusercontent.com/15925454/93955399-3ed5db80-fd82-11ea-9eff-a559d616815e.png)
   
   it's has this bug with mysql-connector-java-5.1.46.jar.
   
![image](https://user-images.githubusercontent.com/15925454/94116867-1f23dd80-fe7e-11ea-8631-e02d4b5790a8.png)
   
   I only want databasechangeloglock route to wms_base.
   
   
   
   
   


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