RuoYi-Vue-Plus/ruoyi-site/ruoyi-h5/doc/h5_fonts.sql
2025-11-25 17:05:23 +08:00

45 lines
2.0 KiB
SQL
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/*
Navicat Premium Data Transfer
Source Server : localhost
Source Server Type : MySQL
Source Server Version : 80023
Source Host : localhost:3306
Source Schema : h5
Target Server Type : MySQL
Target Server Version : 80023
File Encoding : 65001
Date: 14/11/2025 15:00:00
*/
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;
-- ----------------------------
-- Table structure for h5_font
-- ----------------------------
DROP TABLE IF EXISTS `h5_font`;
CREATE TABLE `h5_font`
(
`id` bigint NOT NULL AUTO_INCREMENT COMMENT '主键ID',
`source_id` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '字体来源',
`name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '字体名称',
`preview` json NOT NULL COMMENT '预览JSON格式',
`lang` varchar(10) NOT NULL COMMENT '字体语言类型zh-中文en-英文',
`alias` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '字体别名',
`content` json NOT NULL COMMENT '字体内容JSON格式',
`create_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间戳',
`update_time` DATETIME ON UPDATE CURRENT_TIMESTAMP NULL COMMENT '更新时间戳',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_name` (`name`) USING BTREE COMMENT '字体族名称唯一索引',
INDEX `idx_lang` (`lang`) USING BTREE COMMENT '语言类型索引',
INDEX `idx_name` (`name`) USING BTREE COMMENT '字体名称索引'
) ENGINE = InnoDB
CHARACTER SET = utf8mb4
COLLATE = utf8mb4_general_ci COMMENT = '字体表'
ROW_FORMAT = Dynamic;
SET FOREIGN_KEY_CHECKS = 1;