ShardingSphere-Proxy分表场景测试案例

快速入门文章参考：《ShardingSphereProxy:快速入门》

基于K8S部署文章参考：《基于K8s部署ShardingSphere-Proxy》

基于golang的测试用例参考：《ShardingSphere-Proxy 连接实战：从 Golang 原生 SQL 到 GORM 的应用》

背景

我们需要具体的看一下ShardingSphere-Proxy分表组件的边界，因此，我测试了常用的41个场景。

数据库表结构

我们对订单表（orders）基于 user_id 进行了分表操作，共分为四张表。而用户表（user）和产品表（product）则未进行分表处理，它们的建表语句如下：

DROP TABLE IF EXISTS `orders`;
CREATE TABLE `orders_0`  (
  `id` bigint NOT NULL,
  `order_id` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
  `user_id` int NOT NULL,
  `product_id` int NOT NULL,
  `order_date` bigint NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic;

DROP TABLE IF EXISTS `user`;
CREATE TABLE `user`  (
  `id` bigint NOT NULL,
  `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic;

DROP TABLE IF EXISTS `product`;
CREATE TABLE `product`  (
  `id` bigint NOT NULL,
  `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic;

测试场景