[GitHub] [shardingsphere] lwtdev edited a comment on issue #7731: How to configure no sharding schema in 5.0.0-RC1

[GitBox <gi...@apache.org>]

lwtdev edited a comment on issue #7731:
URL: https://github.com/apache/shardingsphere/issues/7731#issuecomment-706511640


   > no sharding schema you mentioned means defaultDataSourceName: ds_0, doesn't it?
   
   Yes, Some of the databases in our project need to be sharding and some do not, we want to manage them all with ShardingSphere 
    proxy.
   
   > In your case, does customer exist in any data source? 
   
   Yes, table `customer` alrealy exist before ShardingSphere proxy started.
   
   ```sql
   mysql> show tables;
   +--------------------------------+
   | Tables_in_spsqltest_nosharding |
   +--------------------------------+
   | customer                       |
   | customer_email                 |
   | full_table                     |
   +--------------------------------+
   3 rows in set (0.01 sec)
   
   mysql> select * from customer;
   Empty set (0.01 sec)
   
   mysql> drop table customer;
   ERROR 1235 (42000): This version of ShardingProxy doesn't yet support this SQL. 'Cannot find table rule with logic table: 'customer''
   ```
   
   > Consequently, If you have a table customer in a certain data source, ShardingSphere will know its position after startup. Next, you execute drop table customer, it will position this table and run your SQL.
   What do you think?
   
   Because before we used additional database version management tools to manage the table structure.
   So I have to learn more about this.
   - What is the situation of ShardingSphere Jdbc.
   - Whether to support online change table structure (add, modify, delete)
   - How to synchronize the metadata of each node of the ShardingSphere Proxy cluster.
   - Is there a synchronization method for modifying the external table structure of ShardingSphere without new startup (such as timing, manual or monitoring)?
   


----------------------------------------------------------------
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:
users@infra.apache.org