ufutx/migrate
4
0
Fork 0
Code Issues Pull Requests Projects Releases Activity

Merge branch 'main' of https://gitea.ufutx.net/ufutx/migrate

Browse Source
This commit is contained in:
tg130 2024-08-02 18:20:37 +08:00
commit c4c201333d
9 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
1722052698_create_test_table.down.sql
View File

@ -1 +0,0 @@
drop table if EXISTS ufutx_test;

5
1722052698_create_test_table.up.sql
View File

@ -1,5 +0,0 @@
create table if not EXISTS ufutx_test (
id int(10) unsigned not null auto_increment,
name varchar(100) not null comment "姓名",
primary key(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

1
1722060174_table_add_gender.down.sql
View File

@ -1 +0,0 @@
alter table ufutx_test drop column gender

1
1722060174_table_add_gender.up.sql
View File

@ -1 +0,0 @@
alter table ufutx_test add column gender tinyint default 1 comment "性别"

5
1722234431_create_test_table.down.sql
View File

@ -1,5 +0,0 @@
create table if not EXISTS ufutx_test (
id int(10) unsigned not null auto_increment,
name varchar(100) not null comment "姓名",
primary key(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

1
1722234431_create_test_table.up.sql
View File

@ -1 +0,0 @@
drop table if EXISTS ufutx_test;

3
1722503530_change_table_notice_center.up.sql Normal file
View File

@ -0,0 +1,3 @@
ALTER TABLE `ufutx_notice_center_log` ADD COLUMN `from_user_id` int(11) NULL COMMENT '发送方用户id' AFTER `source`,
ADD INDEX `user_id`(`user_id`) USING BTREE,
ADD INDEX `source`(`source`) USING BTREE;

1
1722579359_table_ufutx_s2_shop_sku_add_pay_c2c.up.sql Normal file
View File

@ -0,0 +1 @@
alter table `ufutx_s2_shop_sku` add COLUMN `pay_c2c` tinyint default 0 comment "是否支持对公转账,0:不支持,1:支持" AFTER `status`

1
1722579383_table_ufutx_s2_shop_order_add_pay_type.up.sql Normal file
View File

@ -0,0 +1 @@
alter table `ufutx_s2_shop_order` add COLUMN `pay_type` tinyint default 1 comment "支付类型,1:微信支付,2:对公转账" AFTER `status`