cay914 opened a new issue #6539:
URL: https://github.com/apache/shardingsphere/issues/6539


   Now, i use the navicat 11.1 version.
   
   Ok, this time i can connect to sharding-proxy server.
   Now, sharding-proxy shocking me.
   
![image](https://user-images.githubusercontent.com/6037435/88952030-6a2fd300-d2c9-11ea-89f8-395c405671e8.png)
   
   the table 't_order' ddl
   
   CREATE TABLE `order` (  `order_id` int(20) NOT NULL COMMENT '自动编号',  
`user_id` bigint(20) NOT NULL COMMENT '客户编号',  `shop_id` bigint(20) NOT NULL 
COMMENT '商店编号',  `product_count` int(11) NOT NULL COMMENT '商品数量',  
`product_amount_total` decimal(5,2) NOT NULL COMMENT '商品总价',  
`order_amount_total` decimal(5,2) NOT NULL COMMENT '订单金额',  `logistics_fee` 
decimal(5,2) DEFAULT NULL COMMENT '运费金额',  `is_unpacking_inspection` tinyint(1) 
DEFAULT NULL COMMENT '是否开箱验货',  `is_invoice` tinyint(1) DEFAULT NULL COMMENT 
'是否开具发票',  `invoice_no` varchar(50) DEFAULT NULL COMMENT '发票编号',  `address_id` 
bigint(20) DEFAULT NULL COMMENT '收货地址编号',  `logistics_id` bigint(20) DEFAULT 
NULL COMMENT '订单物流编号',  `pay_channel` varchar(50) DEFAULT NULL COMMENT 
'订单支付渠道',  `escrow_trade_no` varchar(50) 
 DEFAULT NULL COMMENT '订单支付单号',  `create_time` datetime DEFAULT NULL COMMENT 
'创建时间/下单时间',  `pay_time` datetime DEFAULT NULL COMMENT '付款时间',  `deliver_time` 
datetime DEFAULT NULL COMMENT '发货时间',  `settlement_status` varchar(20) DEFAULT 
NULL COMMENT '货到付款、分期付款会使用',  `settlement_time` datetime DEFAULT NULL COMMENT 
'订单结算时间',  PRIMARY KEY (`order_id`),  KEY `user_id` (`user_id`) USING BTREE) 
ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
   --
   
   
   the setting file is:
   
[sharding-proxy.zip](https://github.com/apache/shardingsphere/files/5002715/sharding-proxy.zip)
   
   conclusion:
   create table is ok, but insert data is **TOO BAD**。
   
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to