Raigor

Yes, as long as it is a `sharding table`, explicit configuration is required. Only `single table` does not need to be configured.

> Will you consider optimizing this in the future? Our current database has more than 1000 tables. If we want to divide the database horizontally to reduce the pressure on...

Closed due to no reply for a long time.

Yes, `maxsize` is not supported by the current syntax definition, are you interested in improving it? refer to https://github.com/apache/shardingsphere/blob/master/shardingsphere-sql-parser/shardingsphere-sql-parser-dialect/shardingsphere-sql-parser-opengauss/src/main/antlr4/imports/opengauss/DDLStatement.g4

Hi @zhqiang-li I see that you are using druid-spring-boot-starter, please see if the FAQ helps? https://shardingsphere.apache.org/document/current/en/reference/faq/#jdbc-why-there-may-be-an-error-when-configure-both-shardingsphere-jdbc-spring-boot-starter-and-a-spring-boot-starter-of-certain-datasource-poolsuch-as-druid

@yx9o Thank you, let me explain, this task needs to add the corresponding distsql module under global rule, you may need to add new SPI, like `EncryptDistSQLStatementParserFacade`

@yx9o Completed, thank you!

As far as I know, helm does not support special YAML tags like `!TRANSTACTION`. This problem may be resolved in the next version.

@clytzelbj In fact, only `mode` and `authority` must be configured in `server.yaml`. Other global rules can be configured by DistSQL , which should solve your problem. Please refer to [ALTER...

Closed due to no reply for a long time.