Exactly true. ShardingSphere only returns the metadata of actual table 
currently. We expect someone who is interested in it can do some contributions 
to make it better. :) 


Welcome. 


 Juan Pan


panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere


On 11/20/2019 14:11??sushixiang<shixian...@qq.com> wrote??
Thanks for replying.


But, there are also some problems.If my sql is "select * from 
information_schema.columns where table_name = 't_order'", shardingsphere will 
not response the correct result while the t_oder is a sharding table, because 
the physical table name may be t_order_0. It may be not elegant for using the 
physical table name.




------------------&nbsp;Original&nbsp;------------------
From:&nbsp;"Juan Pan"<panj...@apache.org&gt;;
Date:&nbsp;Wed, Nov 20, 2019 02:03 PM
To:&nbsp;"dev@shardingsphere.apache.org"<dev@shardingsphere.apache.org&gt;;
Cc:&nbsp;"dev"<dev@shardingsphere.apache.org&gt;;
Subject:&nbsp;Re:How does shardingsphere handle queries about information_shema 
?



Hi did you use MySQL??
Please add item of `defaultDataSource` to your shardingRule configuration. When 
ShardingSphere doesn??t find any sharding table named `column`, it will send 
query to default datasource, i.e `innformation_schema`.


&nbsp;Juan Pan


panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere


On 11/20/2019 13:47??sushixiang<shixian...@qq.com&gt; wrote??
How does shardingsphere handle queries about information_shema ?


Now, when I query from tables in information_schema, exception like "Table 
'information.column' doesn't exist"&amp;nbsp;will cause.


So, does shardingsphere deal with the information_shema query scene??

Reply via email to