记得上下班打卡 | git大法好,push需谨慎

Commit 3f704080 authored by wanglele's avatar wanglele

兑换码sku--->时间

parent 5db1f669
use use
dev_ln_scene; dev_ln_scene;
-- >>------------------------------------------------------------------------------------ -- >>------------------------------------------------------------------------------------
...@@ -12,17 +12,17 @@ CREATE TABLE goblin_nft_ex_code ...@@ -12,17 +12,17 @@ CREATE TABLE goblin_nft_ex_code
sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '款式id', sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '款式id',
box_sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '盲盒抽取的款式id', box_sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '盲盒抽取的款式id',
code VARCHAR(64) NOT NULL DEFAULT '' COMMENT '兑换码', code VARCHAR(64) NOT NULL DEFAULT '' COMMENT '兑换码',
state TINYINT UNSIGNED DEFAULT 1 comment '兑换码状态 1未兑换 2已兑换 3已失效', state TINYINT UNSIGNED DEFAULT 1 comment '兑换码状态 1未兑换 2已兑换 3已失效',
redeem_uid VARCHAR(64) NOT NULL DEFAULT '' COMMENT '兑换用户id', redeem_uid VARCHAR(64) NOT NULL DEFAULT '' COMMENT '兑换用户id',
redeem_at DATETIME NULL DEFAULT NULL COMMENT '兑换时间', redeem_at DATETIME NULL DEFAULT NULL COMMENT '兑换时间',
admin_uid VARCHAR(64) NOT NULL DEFAULT '' COMMENT '操作用户id', admin_uid VARCHAR(64) NOT NULL DEFAULT '' COMMENT '操作用户id',
created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间', created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间',
updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间', updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间',
KEY `idx_nft_code_id` (`code_id`), KEY `idx_nft_code_id` (`code_id`),
KEY `idx_nft_activity_id` (`activity_id`), KEY `idx_nft_activity_id` (`activity_id`),
KEY `idx_nft_sku_id` (`sku_id`), KEY `idx_nft_sku_id` (`sku_id`),
KEY `idx_nft_code` (`code`), KEY `idx_nft_code` (`code`),
KEY `idx_nft_redeem_uid` (`redeem_uid`) KEY `idx_nft_redeem_uid` (`redeem_uid`)
) ENGINE = InnoDB ) ENGINE = InnoDB
DEFAULT CHARSET utf8mb4 DEFAULT CHARSET utf8mb4
COLLATE utf8mb4_unicode_ci COLLATE utf8mb4_unicode_ci
...@@ -36,9 +36,9 @@ CREATE TABLE goblin_nft_ex_activity ...@@ -36,9 +36,9 @@ CREATE TABLE goblin_nft_ex_activity
mid BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY, mid BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
activity_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动id', activity_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动id',
title VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动标题', title VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动标题',
created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间', created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间',
updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间', updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间',
KEY `idx_nft_activity_id` (`activity_id`) KEY `idx_nft_activity_id` (`activity_id`)
) ENGINE = InnoDB ) ENGINE = InnoDB
DEFAULT CHARSET utf8mb4 DEFAULT CHARSET utf8mb4
COLLATE utf8mb4_unicode_ci COLLATE utf8mb4_unicode_ci
...@@ -48,21 +48,43 @@ DROP TABLE IF EXISTS goblin_nft_ex_sku; ...@@ -48,21 +48,43 @@ DROP TABLE IF EXISTS goblin_nft_ex_sku;
CREATE TABLE goblin_nft_ex_sku CREATE TABLE goblin_nft_ex_sku
( (
mid BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY, mid BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
activity_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动id', activity_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '活动id',
store_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '店铺id', store_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '店铺id',
spu_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '商品id', spu_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '商品id',
sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '款式id', sku_id VARCHAR(64) NOT NULL DEFAULT '' COMMENT '款式id',
unbox CHAR NOT NULL DEFAULT '0' comment '是否盲盒[0-否|1-是]', unbox CHAR NOT NULL DEFAULT '0' comment '是否盲盒[0-否|1-是]',
ex_stock INT UNSIGNED NOT NULL DEFAULT 0 COMMENT '兑换库存', ex_stock INT UNSIGNED NOT NULL DEFAULT 0 COMMENT '兑换库存',
ex_limit INT UNSIGNED NOT NULL DEFAULT 0 COMMENT '兑换限购', ex_limit INT UNSIGNED NOT NULL DEFAULT 0 COMMENT '兑换限购',
ex_start_time DATETIME NULL DEFAULT NULL COMMENT '兑换生效开始时间', ex_start_time DATETIME NULL DEFAULT NULL COMMENT '兑换生效开始时间',
ex_stop_time DATETIME NULL DEFAULT NULL COMMENT '兑换生效结束时间', ex_stop_time DATETIME NULL DEFAULT NULL COMMENT '兑换生效结束时间',
created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间', created_at DATETIME NULL DEFAULT NULL COMMENT '创建时间',
updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间', updated_at DATETIME NULL DEFAULT NULL COMMENT '更新时间',
KEY `idx_nft_ex_activity_id` (`activity_id`), KEY `idx_nft_ex_activity_id` (`activity_id`),
KEY `idx_nft_ex_spu_id` (`spu_id`), KEY `idx_nft_ex_spu_id` (`spu_id`),
KEY `idx_nft_ex_sku_id` (`sku_id`) KEY `idx_nft_ex_sku_id` (`sku_id`)
) ENGINE = InnoDB ) ENGINE = InnoDB
DEFAULT CHARSET utf8mb4 DEFAULT CHARSET utf8mb4
COLLATE utf8mb4_unicode_ci COLLATE utf8mb4_unicode_ci
ROW_FORMAT = DYNAMIC COMMENT 'NFT兑换活动关联SKU表'; ROW_FORMAT = DYNAMIC COMMENT 'NFT兑换活动关联SKU表';
\ No newline at end of file
DROP TABLE IF EXISTS `goblin_nft_ex_code_task`;
CREATE TABLE `goblin_nft_ex_code_task`
(
`mid` bigint(0) NOT NULL AUTO_INCREMENT,
`task_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT '定时id',
`activity_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT '活动id',
`store_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT '店铺id',
`spu_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT 'spuid',
`sku_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT 'skuid',
`unbox` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL COMMENT '是否盲盒[0-否|1-是]',
`ex_stock` int(0) NOT NULL COMMENT '兑换库存',
`ex_limit` int(0) NOT NULL COMMENT '兑换限购',
`ex_start_time` datetime(0) NOT NULL COMMENT '兑换生效开始时间',
`ex_stop_time` datetime(0) NOT NULL COMMENT '兑换生效结束时间',
`typ` tinyint(0) NULL DEFAULT NULL COMMENT '是否生效 0:否 1:是',
`created_at` datetime(0) NOT NULL COMMENT '创建时间',
`updated_at` datetime(0) NULL DEFAULT NULL COMMENT '修改时间',
PRIMARY KEY (`mid`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci COMMENT = '兑换码定时任务表' ROW_FORMAT = Dynamic;
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment