Click4NB 1.3 发布

最新推荐文章于 2024-12-11 22:29:44 发布
转载 最新推荐文章于 2024-12-11 22:29:44 发布 · 92 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/dushu/archive/2012/12/20/2826124.html

Click4NB为Click开发人员提供了一个除官方ClickIDE外的选择。最新版本Click4NB1.3已发布，支持NetBeans7.2环境。用户可以下载click4nb-1.1.3.0-nb72-updates.zip文件进行安装。

Click4NB 为 Click 开发人员提供了官方 ClickIDE（Click 框架的Eclispe 插件） 之外一种选择。

Click4NB 1.3 发布了，该版本支持 NetBeans 7.2 。

下载地址：click4nb-1.1.3.0-nb72-updates.zip   1.7 MB

转载于:https://www.cnblogs.com/dushu/archive/2012/12/20/2826124.html

badiu_30394251
关注
大数据领域Lambda架构的未来发展趋势展望
AI天才研究院
04-22 634
Lambda架构自2011年由Nathan Marz提出以来，长期作为大数据实时处理的经典范式，广泛应用于金融风控、电商推荐、物联网监控等场景。随着数据量呈指数级增长（IDC预测2025年全球数据量将达175ZB）、实时性要求从“准实时”向“毫秒级”演进，以及流批一体技术（如Apache Flink、Spark Structured Streaming）的成熟，Lambda架构面临新的挑战与机遇。
Web-拾贝
oscar999的专栏
03-10 1万+
JavaScript MVC框架PK：Angular、Backbone、CanJS与Emberhttp://www.csdn.net/article/2013-04-25/2815032-A-Comparison-of-Angular-Backbone-CanJS-and-Ember一个好的js method 方法查询的网站， 有browser兼容的介绍http://help.dottoro.co...
click4nb 1.1.1 发布
hantsy的专栏
05-19 109
Click4nb 是一个Apache Click 框架的 NetBeans IDE插件。 详细情况请参考： http://blog.chinaunix.net/u/1096/showart_2234426.html
Zeta Debugger 1.3
Linhanshi Blog
07-30 887
Zeta Debugger is a stand-alone source level debugger and code profiler for Windows 98/2000/XP applications written in C/C++ or assembly languages. Source level debugging is allowed when symbolic de
逐行逐句从BEVFormer开始学起（二）
热门推荐
lovely_yoshino的博客
12-11 1万+
随着Transformer爆火，也导致了许多以Transformer为主题框架的端到端网络的兴起，这也导致了传统自动驾驶模块化逐渐被取代，这里我们将围绕BEVFormer开始学习整体的架构，我们在上一讲《》中介绍了数据端输入。下面我们来继续学习图像特征提取与位置编码。
【运行代码】LaMOO-Multi-objective Optimization by Learning Space Partitions，环境配置
Drug discovery
11-05 434
运行代码的时候出现了很多的错误“此处记录conda环境是什么。
arduino（6）：使用ESP8266，连接wifi，并通过 mqtt 协议发送消息，通过 MQTTBox 控制 LED 开关，实现设备控制。
freewebsys的专栏
02-04 5380
目录前言1，关于arduino mqtt2，使用 eclipse-mosquitto 镜像2，使用 PubSubClient3，总结 前言 相关arduino 全部分类： https://blog.csdn.net/freewebsys/category_8799254.html 本文的原文连接是: https://blog.csdn.net/freewebsys/article/detail...
初识mapbox GL
LZUGIS
03-24 4405
一、概述 最近由于项目的需求，借此机会对mapbox GL做了一个系统的学习，同时也对整个学习过程做一个记录，一方面留作自用，另一方面也希望看到此文的人在学习mapbox GL的时候，能够有所启发、有所收获。 二、快速认识 很多人在学习一个新的webis框架的时候，表示狗咬刺猬——无从下口。对于这一点，我的建议是快速认识。 1.目的 快速认识的目的有两个：1、对框架有一个认知性的理解；2、甄别框架...
FCKeditor2.4.2 For Asp.net发布了（附各个本版特征）
weixin_34187862的博客
11-27 326
概述：FCKeditor是一款功能强大的在线HTML编辑器，在博客日益兴盛的web2.0时代FCKeditor已经开始走向普通人的视线。FCKeditor文本编辑程序（共享软件）为用户提供在线的文档编辑服务，其具有与微软office软件一样的功能，与之不同的是FCKeditor不需要用户安装任何形式的客户端，FCKeditor程序非常精简但功能强大，...
【STM32F4触摸屏应用开发实战】：探索者开发板上的高级实践
!... # 摘要 本文主要探讨了基于STM32F4微控制器的触摸屏应用开发。首先，本文概述了触摸屏应用开发的概念，并介绍了STM32F4开发板及其硬件环境的搭建。接着，深入分析了触摸屏驱动的开发与集成过程，包括理论基础、...
卸载NetBeans7.3.1出错
游海东的技术专栏
11-23 5433
由于NetBeans的版本更新，我想卸掉原来的版本NetBeans7.3.1，进入Windows7的控制面板，进行卸载。但是，我试过好几次，都卸载不了，并且一直出现错误提示 1、错误提示图 2、错误日志 20131122234001.log [2013-11-22 23:40:01.925]: entering -- org.netbeans.installer.Install
/* Navicat Premium Data Transfer Source Server : localhost_3306 Source Server Type : MySQL Source Server Version : 80017 Source Host : localhost:3306 Source Schema : nb Target Server Type : MySQL Target Server Version : 80017 File Encoding : 65001 Date: 15/05/2025 17:57:59 */ SET NAMES utf8mb4; SET FOREIGN_KEY_CHECKS = 0; – Table structure for admin DROP TABLE IF EXISTS admin; CREATE TABLE admin ( id int(11) NOT NULL AUTO_INCREMENT, username varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘用户名’, password varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘密码’, real_name varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘真实姓名’, contact_info varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘联系方式’, role_id int(11) NOT NULL DEFAULT 2 COMMENT ‘角色ID(默认为管理员)’, create_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘创建时间’, update_time datetime NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘更新时间’, PRIMARY KEY (id) USING BTREE, UNIQUE INDEX username(username ASC) USING BTREE, INDEX role_id(role_id ASC) USING BTREE, CONSTRAINT admin_ibfk_1 FOREIGN KEY (role_id) REFERENCES role (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘管理员表’ ROW_FORMAT = Dynamic; – Records of admin – Table structure for device DROP TABLE IF EXISTS device; CREATE TABLE device ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘设备名称’, category_id int(11) NOT NULL COMMENT ‘分类ID’, model varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘设备型号’, status varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT ‘IN_STOCK’ COMMENT ‘设备状态(IN_STOCK, IN_USE, MAINTENANCE, SCRAPPED)’, location varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘存放位置’, quantity int(11) NULL DEFAULT 1 COMMENT ‘数量’, purchase_date date NULL DEFAULT NULL COMMENT ‘采购日期’, price decimal(10, 2) NULL DEFAULT NULL COMMENT ‘单价’, description text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT ‘设备描述’, create_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘创建时间’, update_time datetime NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘更新时间’, PRIMARY KEY (id) USING BTREE, INDEX category_id(category_id ASC) USING BTREE, CONSTRAINT device_ibfk_1 FOREIGN KEY (category_id) REFERENCES device_category (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘设备表’ ROW_FORMAT = Dynamic; – Records of device – Table structure for device_category DROP TABLE IF EXISTS device_category; CREATE TABLE device_category ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘分类名称’, parent_id int(11) NULL DEFAULT NULL COMMENT ‘父分类ID，用于多级分类’, description varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘分类描述’, create_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘创建时间’, update_time datetime NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘更新时间’, PRIMARY KEY (id) USING BTREE, UNIQUE INDEX name(name ASC) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘设备分类表’ ROW_FORMAT = Dynamic; – Records of device_category – Table structure for device_repair DROP TABLE IF EXISTS device_repair; CREATE TABLE device_repair ( id int(11) NOT NULL AUTO_INCREMENT, device_id int(11) NOT NULL COMMENT ‘设备ID’, apply_user_id int(11) NOT NULL COMMENT ‘申请用户ID’, apply_user_type enum(‘regular_user’,‘admin’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘申请用户类型’, apply_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘申请时间’, description text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT ‘故障描述’, status enum(‘PENDING’,‘APPROVED’,‘REJECTED’,‘COMPLETED’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT ‘PENDING’ COMMENT ‘状态’, approve_operator_id int(11) NULL DEFAULT NULL COMMENT ‘审批人ID’, approve_time datetime NULL DEFAULT NULL COMMENT ‘审批时间’, repair_operator_id int(11) NULL DEFAULT NULL COMMENT ‘维修人员ID’, repair_time datetime NULL DEFAULT NULL COMMENT ‘维修完成时间’, cost decimal(10, 2) NULL DEFAULT NULL COMMENT ‘维修费用’, remark varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘备注’, PRIMARY KEY (id) USING BTREE, INDEX device_id(device_id ASC) USING BTREE, CONSTRAINT device_repair_ibfk_1 FOREIGN KEY (device_id) REFERENCES device (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘设备维修记录表’ ROW_FORMAT = Dynamic; – Records of device_repair – Table structure for device_scrap DROP TABLE IF EXISTS device_scrap; CREATE TABLE device_scrap ( id int(11) NOT NULL AUTO_INCREMENT, device_id int(11) NOT NULL COMMENT ‘设备ID’, apply_user_id int(11) NOT NULL COMMENT ‘申请用户ID’, apply_user_type enum(‘regular_user’,‘admin’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘申请用户类型’, apply_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘申请时间’, reason varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘报废原因’, status enum(‘PENDING’,‘APPROVED’,‘REJECTED’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT ‘PENDING’ COMMENT ‘状态’, approve_operator_id int(11) NULL DEFAULT NULL COMMENT ‘审批人ID’, approve_time datetime NULL DEFAULT NULL COMMENT ‘审批时间’, scrap_time datetime NULL DEFAULT NULL COMMENT ‘报废时间’, remark varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘备注’, PRIMARY KEY (id) USING BTREE, INDEX device_id(device_id ASC) USING BTREE, CONSTRAINT device_scrap_ibfk_1 FOREIGN KEY (device_id) REFERENCES device (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘设备报废表’ ROW_FORMAT = Dynamic; – Records of device_scrap – Table structure for device_transfer DROP TABLE IF EXISTS device_transfer; CREATE TABLE device_transfer ( id int(11) NOT NULL AUTO_INCREMENT, device_id int(11) NOT NULL COMMENT ‘设备ID’, from_location varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘调出位置’, to_location varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘调入位置’, apply_user_id int(11) NOT NULL COMMENT ‘申请用户ID’, apply_user_type enum(‘regular_user’,‘admin’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘申请用户类型’, apply_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘申请时间’, quantity int(11) NOT NULL COMMENT ‘调拨数量’, status enum(‘PENDING’,‘APPROVED’,‘REJECTED’,‘COMPLETED’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT ‘PENDING’ COMMENT ‘状态’, approve_operator_id int(11) NULL DEFAULT NULL COMMENT ‘审批人ID’, approve_time datetime NULL DEFAULT NULL COMMENT ‘审批时间’, transfer_time datetime NULL DEFAULT NULL COMMENT ‘调拨完成时间’, remark varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘备注’, PRIMARY KEY (id) USING BTREE, INDEX device_id(device_id ASC) USING BTREE, CONSTRAINT device_transfer_ibfk_1 FOREIGN KEY (device_id) REFERENCES device (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘设备调拨表’ ROW_FORMAT = Dynamic; – Records of device_transfer – Table structure for inbound_record DROP TABLE IF EXISTS inbound_record; CREATE TABLE inbound_record ( id int(11) NOT NULL AUTO_INCREMENT, device_id int(11) NOT NULL COMMENT ‘设备ID’, quantity int(11) NOT NULL COMMENT ‘入库数量’, operator_id int(11) NOT NULL COMMENT ‘操作人ID’, operator_type enum(‘regular_user’,‘admin’,‘manager’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘操作人类型’, inbound_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘入库时间’, remark varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘备注’, status enum(‘PENDING’,‘APPROVED’,‘REJECTED’) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT ‘APPROVED’ COMMENT ‘状态(待审核/已通过/已拒绝)’, audit_operator_id int(11) NULL DEFAULT NULL COMMENT ‘审核人ID’, audit_time datetime NULL DEFAULT NULL COMMENT ‘审核时间’, PRIMARY KEY (id) USING BTREE, INDEX device_id(device_id ASC) USING BTREE, CONSTRAINT inbound_record_ibfk_1 FOREIGN KEY (device_id) REFERENCES device (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘入库记录表’ ROW_FORMAT = Dynamic; – Records of inbound_record – Table structure for manager DROP TABLE IF EXISTS manager; CREATE TABLE manager ( id int(11) NOT NULL AUTO_INCREMENT, username varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘用户名’, password varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘密码’, real_name varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘真实姓名’, contact_info varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘联系方式’, role_id int(11) NOT NULL DEFAULT 3 COMMENT ‘角色ID(默认为经理)’, create_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘创建时间’, update_time datetime NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘更新时间’, PRIMARY KEY (id) USING BTREE, UNIQUE INDEX username(username ASC) USING BTREE, INDEX role_id(role_id ASC) USING BTREE, CONSTRAINT manager_ibfk_1 FOREIGN KEY (role_id) REFERENCES role (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘经理表’ ROW_FORMAT = Dynamic; – Records of manager – Table structure for permission DROP TABLE IF EXISTS permission; CREATE TABLE permission ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘权限名称’, code varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘权限代码’, description varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘权限描述’, PRIMARY KEY (id) USING BTREE, UNIQUE INDEX code(code ASC) USING BTREE ) ENGINE = InnoDB AUTO_INCREMENT = 15 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘权限表’ ROW_FORMAT = Dynamic; – Records of permission INSERT INTO permission VALUES (1, ‘login’, ‘user:login’, ‘用户登录’); INSERT INTO permission VALUES (2, ‘logout’, ‘user:logout’, ‘用户退出’); INSERT INTO permission VALUES (3, ‘edit_profile’, ‘user:edit-profile’, ‘修改个人信息’); INSERT INTO permission VALUES (4, ‘view_records’, ‘record:view’, ‘查看出入库记录’); INSERT INTO permission VALUES (5, ‘query_records’, ‘record:query’, ‘查询出入库记录’); INSERT INTO permission VALUES (6, ‘inbound_device’, ‘device:inbound’, ‘设备入库’); INSERT INTO permission VALUES (7, ‘apply_transfer’, ‘device:apply-transfer’, ‘申请设备调拨’); INSERT INTO permission VALUES (8, ‘apply_repair’, ‘device:apply-repair’, ‘申请设备维修’); INSERT INTO permission VALUES (9, ‘apply_scrap’, ‘device:apply-scrap’, ‘申请设备报废’); INSERT INTO permission VALUES (10, ‘manage_users’, ‘user:manage’, ‘管理用户账号’); INSERT INTO permission VALUES (11, ‘manage_categories’, ‘category:manage’, ‘管理设备分类’); INSERT INTO permission VALUES (12, ‘manage_devices’, ‘device:manage’, ‘管理设备信息’); INSERT INTO permission VALUES (13, ‘audit_records’, ‘record:audit’, ‘审核出入库记录’); INSERT INTO permission VALUES (14, ‘approve_requests’, ‘request:approve’, ‘审批申请’); INSERT INTO permission VALUES (20, ‘查询设备信息’, ‘device:query’, ‘普通用户查看仓库内设备的详细信息，包括库存数量、位置、状态等’); INSERT INTO permission VALUES (25, ‘添加普通用户账号’, ‘user:add’, ‘管理员为仓库新增普通用户账号，分配初始权限’); INSERT INTO permission VALUES (26, ‘管理仓库基本信息’, ‘warehouse:manage’, ‘管理员管理仓库的基本信息，如仓库容量、布局等’); INSERT INTO permission VALUES (29, ‘管理出入库记录’, ‘record:manage’, ‘管理员管理出入库记录，包括审核、修改和删除操作’); INSERT INTO permission VALUES (30, ‘审核设备入库’, ‘inbound:audit’, ‘管理员监督和审核设备的入库流程，确保操作的合规性’); INSERT INTO permission VALUES (31, ‘查看设备库存数据’, ‘device:data:view’, ‘管理员查看设备的库存数据、上架数据等，为决策提供支持’); INSERT INTO permission VALUES (32, ‘查看仓库运营数据’, ‘warehouse:data:view’, ‘管理员查看仓库的整体运营数据，如库存周转率、利用率等’); INSERT INTO permission VALUES (33, ‘审批设备调拨’, ‘transfer:approve’, ‘管理员执行对普通用户的设备调拨审批工作’); INSERT INTO permission VALUES (34, ‘审批设备维修’, ‘repair:approve’, ‘管理员执行对普通用户的设备维修审批工作’); INSERT INTO permission VALUES (35, ‘审批设备报废’, ‘scrap:approve’, ‘管理员执行对普通用户的设备报废审批工作’); INSERT INTO permission VALUES (36, ‘管理管理员账号’, ‘admin:manage’, ‘经理管理管理员账号，包括修改、删除等’); INSERT INTO permission VALUES (37, ‘添加管理员账号’, ‘admin:add’, ‘经理为系统新增管理员账号，分配初始权限’); INSERT INTO permission VALUES (38, ‘调整普通用户权限’, ‘user:permission:adjust’, ‘经理调整普通用户权限、账号审核等’); – Table structure for regular_user DROP TABLE IF EXISTS regular_user; CREATE TABLE regular_user ( id int(11) NOT NULL AUTO_INCREMENT, username varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘用户名’, password varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘密码’, real_name varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘真实姓名’, contact_info varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘联系方式’, role_id int(11) NOT NULL DEFAULT 1 COMMENT ‘角色ID(默认为普通用户)’, create_time datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT ‘创建时间’, update_time datetime NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT ‘更新时间’, PRIMARY KEY (id) USING BTREE, UNIQUE INDEX username(username ASC) USING BTREE, INDEX role_id(role_id ASC) USING BTREE, CONSTRAINT regular_user_ibfk_1 FOREIGN KEY (role_id) REFERENCES role (id) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘普通用户表’ ROW_FORMAT = Dynamic; – Records of regular_user – Table structure for role DROP TABLE IF EXISTS role; CREATE TABLE role ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT ‘角色名称(普通用户/管理员/经理)’, description varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT ‘角色描述’, PRIMARY KEY (id) USING BTREE ) ENGINE = InnoDB AUTO_INCREMENT = 4 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘角色表’ ROW_FORMAT = Dynamic; – Records of role INSERT INTO role VALUES (1, ‘普通用户’, ‘负责日常出入库操作和记录管理’); INSERT INTO role VALUES (2, ‘管理员’, ‘负责仓库整体运营和管理’); INSERT INTO role VALUES (3, ‘经理’, ‘负责整个仓库管理系统的全局管理和监督’); – Table structure for role_permission DROP TABLE IF EXISTS role_permission; CREATE TABLE role_permission ( role_id int(11) NOT NULL, permission_id int(11) NOT NULL, PRIMARY KEY (role_id, permission_id) USING BTREE, INDEX permission_id(permission_id ASC) USING BTREE, CONSTRAINT role_permission_ibfk_1 FOREIGN KEY (role_id) REFERENCES role (id) ON DELETE CASCADE ON UPDATE RESTRICT, CONSTRAINT role_permission_ibfk_2 FOREIGN KEY (permission_id) REFERENCES permission (id) ON DELETE CASCADE ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = ‘角色权限关联表’ ROW_FORMAT = Dynamic; – Records of role_permission INSERT INTO role_permission VALUES (1, 3); INSERT INTO role_permission VALUES (2, 3); INSERT INTO role_permission VALUES (3, 3); INSERT INTO role_permission VALUES (1, 4); INSERT INTO role_permission VALUES (1, 5); INSERT INTO role_permission VALUES (1, 6); INSERT INTO role_permission VALUES (1, 7); INSERT INTO role_permission VALUES (2, 7); INSERT INTO role_permission VALUES (1, 8); INSERT INTO role_permission VALUES (2, 8); INSERT INTO role_permission VALUES (1, 9); INSERT INTO role_permission VALUES (2, 9); INSERT INTO role_permission VALUES (2, 10); INSERT INTO role_permission VALUES (3, 10); INSERT INTO role_permission VALUES (2, 11); INSERT INTO role_permission VALUES (3, 11); INSERT INTO role_permission VALUES (2, 12); INSERT INTO role_permission VALUES (3, 12); INSERT INTO role_permission VALUES (1, 20); INSERT INTO role_permission VALUES (2, 25); INSERT INTO role_permission VALUES (2, 26); INSERT INTO role_permission VALUES (2, 29); INSERT INTO role_permission VALUES (3, 29); INSERT INTO role_permission VALUES (2, 30); INSERT INTO role_permission VALUES (3, 30); INSERT INTO role_permission VALUES (2, 31); INSERT INTO role_permission VALUES (3, 31); INSERT INTO role_permission VALUES (2, 32); INSERT INTO role_permission VALUES (3, 32); INSERT INTO role_permission VALUES (2, 33); INSERT INTO role_permission VALUES (3, 33); INSERT INTO role_permission VALUES (2, 34); INSERT INTO role_permission VALUES (3, 34); INSERT INTO role_permission VALUES (2, 35); INSERT INTO role_permission VALUES (3, 35); INSERT INTO role_permission VALUES (3, 36); INSERT INTO role_permission VALUES (3, 37); INSERT INTO role_permission VALUES (3, 38); SET FOREIGN_KEY_CHECKS = 1; 根据这个表格 生成一个设备仓储管理系统 用vue java语言实现
05-16
spring.datasource.url=jdbc:mysql://localhost:3306/nb?useSSL=false&serverTimezone=UTC spring.datasource.username=root spring.datasource.password=yourpassword spring.jpa.hibernate.ddl-auto=update spring...
GeneratedClass224.java
01-06
GeneratedClass224.java
ABMeeting免费远程协助软件.rar
01-06
ABMeeting免费远程协助软件.rar
GeneratedClass345.java
01-06
GeneratedClass345.java
Cherry-Studio-1.7.8-amd64.deb
01-06
Cherry-Studio-1.7.8-amd64.deb
运动时的心率监测.zip
01-06
1.版本：matlab2014a/2019b/2024b 2.附赠案例数据可直接运行。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
Python + 基于更换依赖包等方案解决 pycrypto 安装报错！.zip
最新发布
01-06
Python + 基于更换依赖包等方案解决 pycrypto 安装报错！.zip
【顶级EI完美复现】电力系统碳排放流的计算方法【IEEE 14节点】（Matlab代码实现）
01-06
【顶级EI完美复现】电力系统碳排放流的计算方法【IEEE 14节点】（Matlab代码实现）内容概要：本文介绍了基于IEEE 14节点电力系统的碳排放流计算方法，通过Matlab代码实现，旨在对电力系统中各节点的碳排放流动进行建模与仿真分析。该方法能够量化不同电源在电网中的碳排放贡献，支持低碳调度与能源政策制定，属于电力系统环境影响评估的重要研究方向，具备“顶级EI完美复现”的学术价值和技术精度。; 适合人群：电力系统、能源与环境工程领域的研究生、科研人员及从事低碳电网研究的工程师，需具备一定的电力系统基础知识和Matlab编程能力。; 使用场景及目标：①用于电力系统碳排放流的精确建模与可视化；②支撑含新能源接入的低碳调度策略研究；③服务于学术论文复现、课题研究及碳足迹评估等科研任务。; 阅读建议：建议结合IEEE 14节点系统标准数据和Matlab代码同步运行，深入理解碳流分配算法原理，并可进一步拓展至其他节点系统或融合优化算法进行低碳运行分析。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值