diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.cn.md b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.cn.md index 9e0c0a6020db4..3e35cd8800142 100644 --- a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.cn.md +++ b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.cn.md @@ -8,7 +8,7 @@ chapter = true ShardingSphere-JDBC 支持所有的数据库 JDBC 驱动和连接池。 -示例的数据库驱动为 MySQL,连接池为 HikariCP,可以更换为其他数据库驱动和连接池。当使用 ShardingSphere-JDBC 时,JDBC 池的属性名取决于各自 JDBC 池自己的定义,并不由 ShardingSphere 硬定义,相关的处理可以参考类`org.apache.shardingsphere.infra.datasource.pool.creator.DataSourcePoolCreator`。例如对于 Alibaba Druid 1.2.9 而言,使用 `url` 代替如下示例中的 `jdbcUrl` 是预期行为。 +示例的数据库驱动为 MySQL,连接池为 HikariCP,可以更换为其他数据库驱动和连接池。当使用 ShardingSphere-JDBC 时,JDBC 池的属性名取决于各自 JDBC 池自己的定义,并不由 ShardingSphere 定义,相关的处理可以参考类`org.apache.shardingsphere.infra.datasource.pool.creator.DataSourcePoolCreator`。例如对于 Alibaba Druid 1.2.9 而言,使用 `url` 代替如下示例中的 `jdbcUrl` 是预期行为。 ## 参数解释 diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.en.md index e8595212d21f3..ea36212089d1f 100644 --- a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.en.md +++ b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/data-source.en.md @@ -9,7 +9,7 @@ chapter = true ShardingSphere-JDBC Supports all JDBC drivers and data source connection pools. In this example, the database driver is MySQL, and the connection pool is HikariCP, which can be replaced with other database drivers and connection pools. -When using ShardingSphere JDBC, the property name of the JDBC pool depends on the definition of the respective JDBC pool and is not defined by ShardingSphere. For related processing, please refer to the class org.apache.shardingsphere.infra.datasource.pool.creator.DataSourcePoolCreator. +When using ShardingSphere JDBC, the property name of the JDBC pool depends on the definition of the respective JDBC pool and is not defined by ShardingSphere. For related processing, please refer to the class `org.apache.shardingsphere.infra.datasource.pool.creator.DataSourcePoolCreator`. For example, with Alibaba Druid 1.2.9, using url instead of jdbcUrl in the example below is the expected behavior. ## Parameters