首页下载资源前端shenxinfueqswfrfgverw

ZIPshenxinfueqswfrfgverw

weixin_4568604254.86MB需要积分:1

资源文件列表:

shenixnfu.zip 大约有5个文件
  1. shenixnfu/
  2. shenixnfu/report-form-java-1.0-SNAPSHOT.jar 56.02MB
  3. shenixnfu/report_db.sql 25.92KB
  4. shenixnfu/shenxinfu.sh 1.63KB
  5. shenixnfu/shenxinfu.zip 3.96MB

资源介绍:

acerqwerqwerqwtbh
/* Navicat Premium Data Transfer Source Server : 10.0.3.63 Source Server Type : MySQL Source Server Version : 80039 Source Host : 10.0.20.243:3303 Source Schema : report_db Target Server Type : MySQL Target Server Version : 80039 File Encoding : 65001 Date: 31/07/2024 10:07:03 */ SET NAMES utf8mb4; SET FOREIGN_KEY_CHECKS = 0; -- ---------------------------- -- Table structure for qrtz_blob_triggers -- ---------------------------- DROP TABLE IF EXISTS `qrtz_blob_triggers`; CREATE TABLE `qrtz_blob_triggers` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_GROUP` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `BLOB_DATA` blob NULL, PRIMARY KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) USING BTREE, INDEX `SCHED_NAME`(`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) USING BTREE, CONSTRAINT `qrtz_blob_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_blob_triggers -- ---------------------------- -- ---------------------------- -- Table structure for qrtz_calendars -- ---------------------------- DROP TABLE IF EXISTS `qrtz_calendars`; CREATE TABLE `qrtz_calendars` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `CALENDAR_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `CALENDAR` blob NOT NULL, PRIMARY KEY (`SCHED_NAME`, `CALENDAR_NAME`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_calendars -- ---------------------------- -- ---------------------------- -- Table structure for qrtz_cron_triggers -- ---------------------------- DROP TABLE IF EXISTS `qrtz_cron_triggers`; CREATE TABLE `qrtz_cron_triggers` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_GROUP` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `CRON_EXPRESSION` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TIME_ZONE_ID` varchar(80) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, PRIMARY KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) USING BTREE, CONSTRAINT `qrtz_cron_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) ON DELETE RESTRICT ON UPDATE RESTRICT ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_cron_triggers -- ---------------------------- -- ---------------------------- -- Table structure for qrtz_fired_triggers -- ---------------------------- DROP TABLE IF EXISTS `qrtz_fired_triggers`; CREATE TABLE `qrtz_fired_triggers` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `ENTRY_ID` varchar(95) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `TRIGGER_GROUP` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `INSTANCE_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `FIRED_TIME` bigint(0) NOT NULL, `SCHED_TIME` bigint(0) NOT NULL, `PRIORITY` int(0) NOT NULL, `STATE` varchar(16) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `JOB_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, `JOB_GROUP` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, `IS_NONCONCURRENT` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, `REQUESTS_RECOVERY` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, PRIMARY KEY (`SCHED_NAME`, `ENTRY_ID`) USING BTREE, INDEX `IDX_QRTZ_FT_INST_JOB_REQ_RCVRY`(`SCHED_NAME`, `INSTANCE_NAME`, `REQUESTS_RECOVERY`) USING BTREE, INDEX `IDX_QRTZ_FT_JG`(`SCHED_NAME`, `JOB_GROUP`) USING BTREE, INDEX `IDX_QRTZ_FT_J_G`(`SCHED_NAME`, `JOB_NAME`, `JOB_GROUP`) USING BTREE, INDEX `IDX_QRTZ_FT_TG`(`SCHED_NAME`, `TRIGGER_GROUP`) USING BTREE, INDEX `IDX_QRTZ_FT_TRIG_INST_NAME`(`SCHED_NAME`, `INSTANCE_NAME`) USING BTREE, INDEX `IDX_QRTZ_FT_T_G`(`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_fired_triggers -- ---------------------------- -- ---------------------------- -- Table structure for qrtz_job_details -- ---------------------------- DROP TABLE IF EXISTS `qrtz_job_details`; CREATE TABLE `qrtz_job_details` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `JOB_NAME` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `JOB_GROUP` varchar(190) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `DESCRIPTION` varchar(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, `JOB_CLASS_NAME` varchar(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `IS_DURABLE` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `IS_NONCONCURRENT` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `IS_UPDATE_DATA` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `REQUESTS_RECOVERY` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `JOB_DATA` blob NULL, PRIMARY KEY (`SCHED_NAME`, `JOB_NAME`, `JOB_GROUP`) USING BTREE, INDEX `IDX_QRTZ_J_GRP`(`SCHED_NAME`, `JOB_GROUP`) USING BTREE, INDEX `IDX_QRTZ_J_REQ_RECOVERY`(`SCHED_NAME`, `REQUESTS_RECOVERY`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_job_details -- ---------------------------- -- ---------------------------- -- Table structure for qrtz_locks -- ---------------------------- DROP TABLE IF EXISTS `qrtz_locks`; CREATE TABLE `qrtz_locks` ( `SCHED_NAME` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, `LOCK_NAME` varchar(40) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, PRIMARY KEY (`SCHED_NAME`, `LOCK_NAME`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of qrtz_locks -- ---------------------------- INSERT INTO `qrtz_locks` VALUES ('quartzScheduler', 'TRIGGER_ACCESS'); -- ---------------------------- -- Table structure for qrtz_notify_event -- ---------------------------- DROP TABLE IF EXISTS `qrtz_notify_event`; CREATE TABLE `qrtz_notify_event` ( `id` bigint(0) NOT NULL AUTO_INCREMENT, `user_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '登录用户', `application_program` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '应用程序', `trigger_rules` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '触发规则', `login_time` datetime(0) NULL DEFAULT NULL COMMENT '登录时间', `exit_time` datetime(0) NULL DEFAU
100+评论
captcha

    相关资源

    1. termux-app-master.zip

      2401_86552094#行业研究ZIP1.09MB7月前
      资源摘要:termux-app-master.zip

    2. 18715605985定位链接.zip

      2401_86507995#行业研究ZIP11.25KB7月前
      资源摘要:18715605985定位链接.zip

    3. windows操作系统下安装ipmitool工具

      weixin_48724879#后端ZIP967KB7月前
      资源摘要:windows操作系统下安装ipmitool工具

    4. stegdetect图片隐写工具

      mc_dudu233#安全技术ZIP3.48MB7月前
      资源摘要:stegdetect是一款小巧但十分强大的图片隐写检测工具常用来检测图片的加密方法和破解。// 判断是否含有Jphidestegdetect.exe -tjopi -s 10.0 [stego_file]// 爆破密码stegbreak -r rules.ini -f password.txt -t p [stego_file]

    5. centos7系统，nfs服务器所需要依赖安装包，适用于内网环境

      MuderX111#操作系统ZIP3.3MB7月前
      资源摘要:centos7系统，nfs服务器所需要依赖安装包，适用于内网环境。

    6. STM32下推式磁悬浮PCB项目

      qq_63055262#硬件开发ZIP9.69MB7月前
      资源摘要:STM32下推式磁悬浮PCB项目是一个基于嵌入式系统的创新设计，主要利用了STM32微控制器实现磁悬浮效果。STM32是一款基于ARM Cortex-M内核的微控制器，广泛应用于各种电子设备中，以其高性能、低功耗和丰富的外设接口著称。在本项目中，STM32作为核心控制单元，负责处理传感器数据、计算控制算法以及驱动磁悬浮系统。 项目提供的资料包括AD（Altium Designer）工程文件，这是一种专业的电路设计软件，用于绘制原理图和PCB布局。由于文件中不包含封装库，用户在使用AD打开时需要确保自己的环境中已安装了对应的元器件封装库，以便进行完整的电路模拟和PCB制作。 磁悬浮技术主要依赖于电磁力来抵消重力，实现物体的无接触悬浮。在下推式磁悬浮系统中，STM32通过采集传感器数据（例如霍尔效应传感器或电流传感器）来检测悬浮物体的位置和状态，然后通过实时计算调整电磁铁的电流，从而精确控制磁力，使得物体保持稳定悬浮。 在硬件开发过程中，设计者需要考虑的关键因素包括：磁力的计算与控制精度、电源管理、散热设计、安全保护机制以及系统的稳定性。STM32的数字信号处理能力和高速计算能力。

    7. SPI IIC UART RS232/485-详细版

      qq_58662017#硬件开发ZIP42.82MB7月前
      资源摘要:SPI IIC UART RS232/485-详细版

    8. 亚马逊特征词分析工具.zip

      2301_79136259#行业研究ZIP5.39MB7月前
      资源摘要:亚马逊特征词分析工具.zip
    站长QQ:九六九五七三七