FineDB テーブル構造- FineReport Help Document

作成者：ayuan0625

編集回数：23次

最終更新：FRInternational 于 2020-12-29

1. summary

This article briefly introduces the table field description contained in the FineDB database.

Note: due to the different types of external databases, the data types of fields are not completely consistent. In this paper, taking the built-in database as an example, users need to match by themselves.

1.1 Table list

classification	Subcategory	Table name	brief introduction
Authority control	User department position role	FINE_USER	User table
		FINE_EXTRA_PROPERTY	User additional information table
		FINE_DEPARTMENT	Department table
		FINE_POST	Position table
		FINE_DEP_ROLE	The middle table of department position, through which users associate department and job
		FINE_CUSTOM_ROLE	Custom role table
		FINE_USER_ROLE_MIDDLE	The middle table of user roles, through which users are associated with user-defined roles and department job roles
	Permissions directory	FINE_AUTHORITY	Permission table only records the permissions granted to the current directory, and the permissions of templates and subdirectories under the directory will not be recorded
		FINE_AUTHORITY_OBJECT	The permission entity table records the permission object, directory name and report name of the current directory (excluding templates and subdirectories under the directory)
		FINE_AUTH_PREFERENCE	Permissions panel user preferences
		FINE_HOMEPAGE_EXPAND	Home page extension table Record the extended properties of the home page type permission entity
		FINE_FAVORITE_ENTRY	Collection node table
Platform operation	Sign in	FINE_LAST_LOGIN	Last login information table
		FINE_LOGIN_LOCK	Login lock table Locking due to too many password errors Please refer to login lock for details
		FINE_BLOCK_IP	Login lock IP table Locking due to high access frequency of the same IP For details, see: access control
	Backup restore	FINE_BACKUP_NODE	Backup node table
	Scheduled scheduling	FINE_SCHEDULE_TASK	Timing task list
		FINE_SCHEDULE_TASK_PARAM	Scheduled task parameter values
		FINE_SCHEDULE_RECORD	Task execution log
		FINE_SCHEDULE_OUTPUT	Export in timing task
		FINE_BASE_OUTPUT	Task attachment processing main table
		FINE_OUTPUT_CLASS	Custom class processing
		FINE_OUTPUT_CLIENT_NOTICE	client notification
		FINE_OUTPUT_EMAIL	Push mail
		FINE_OUTPUT_FTP	FTP upload
		FINE_OUTPUT_MOUNT	Scheduled task mount directory
		FINE_OUTPUT_PLATFORM_MSG	Platform system messages
		FINE_OUTPUT_PRINT	Print processing
		FINE_OUTPUT_SFTP	SFTP upload
		FINE_OUTPUT_SMS	Send SMS
		FINE_BASE_MESSAGE	Main table of platform message
		FINE_PROCESS_MESSAGE	Report the message
		FINE_SYSTEM_MESSAGE	Platform system messages
		FINE_MOBILE_DEVICE	Mobile device list
	news	FINE_BASE_MESSAGE	Main table of platform message
		FINE_PROCESS_MESSAGE	Report the news
		FINE_SYSTEM_MESSAGE	Platform system messages
	Report	FINE_WORKFLOW	Process in the reporting process
		FINE_WORKFLOW_TASK	Tasks in the reporting process
		FINE_WORKFLOW_TASK_IMPL	Report the tasks in the process and issue the specific tasks
		FINE_WORKFLOW_NODE	Nodes in the reporting process
		FINE_WORKFLOW_STASH_DATA	Data temporary storage in reporting process
		FINE_WORKFLOW_LOG	Operation log in reporting process
system management	to configure	FINE_CONF_CLASSNAME	If the field of configuration class is interface type, record its type
		FINE_CONF_ENTITY	Storing data in configuration classes
		FINE_CONF_XMLENTITY	The structure of some fields is very complex. In order to store them in the database, they are stored as XML
		FINE_INTERNATIONAL	A table for recording multilingual data
	Swift module	FINE_SWIFT_COL_IDX_CONF	Field index configuration
		FINE_SWIFT_CONFIG_ENTITY	Swift internal configuration table
		FINE_SWIFT_METADATA	It is used to store data table metadata
		FINE_SWIFT_SEG_LOCATION	Swift segment distribution information
		FINE_SWIFT_SEGMENTS	Swift segment details
		FINE_SWIFT_SERVICE_INFO	Save swift service information
		FINE_SWIFT_TAB_IDX_CONF	Table index configuration
		FINE_SWIFT_TABLE_PATH	Cube middle directory configuration management
	Quartz module	QRTZ_BLOB_TRIGGERS	Triggers stored in blob type
		QRTZ_CALENDARS	Calendar information storage table
		QRTZ_CRON_TRIGGERS	Store the trigger of cron type
		QRTZ_FIRED_TRIGGERS	Store triggered triggers
		QRTZ_JOB_DETAILS	Store a job detail information
		QRTZ_LOCKS	Store the pessimistic lock information of the program
		QRTZ_PAUSED_TRIGGER_GRPS	Stores information about the pending trigger group
		QRTZ_SCHEDULER_STATE	Note instance information in storage cluster
		QRTZ_SIMPLE_TRIGGERS	Simple trigger information
		QRTZ_SIMPROP_TRIGGERS	Store calendar intervaltrigger and dailytimeintervaltrigger
		QRTZ_TRIGGERS	Basic information of trigger
Other modules	Mobile terminal	FINE_MOBILE_DEVICE	Mobile device list
	Mobile terminal	FINE_MOBILE_PUSH_MESSAGE	Mobile message push table
	report form	FINE_PARAM_TEMPLATE	Template parameter combination
		FINE_PRINT_OFFSET	Print offset
		FINE_PRINT_OFFSET_IP_RELATE	Print offset IP association table
		FINE_REMOTE_DESIGN_AUTH	Remote design user table
		FINE_WRITE_STASH	Fill in the temporary form
		FINE_PROCESS_EXPAND	Extended attribute table of reporting process type permission entity
		FINE_REPORT_EXPAND	Extended attribute table of report type permission entity
		FINE_EXCEL_SUBMIT_TASK	Excel batch import permission entity extension table
		FINE_VCS	Template version management table

1.2 Relationship between tables

1) user

2) Report

3) Scheduled scheduling

4) news

5) Printing

Note: Based on the above table structure, and there is no direct association between the tables, so if direct operation of the database is involved, the data in the intermediate table must be deleted manually.

For example: delete a department = delete Department + delete Dep_Role + delete user_role_middle；

Delete a user = delete user + delete user_role_Middle + delete extra_property。

2. User department position role

2.1 FINE_User table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_extra_property > relatedId fine_user_role_middle > userId fine_base_message > userId fine_auth_preference > userId fine_favorite_entry > userId fine_last_login > userId fine_login_lock > userId fine_workflow_task > creatorId
BIRTHDAY	birthday	TIMESTAMP	26	FALSE	-
CREATIONTYPE	build type 1 - Create manually 2 - Synchronous creation	INTEGER	32	TRUE	-
DESCRIPTION	describe	VARCHAR	1000	FALSE	-
EMAIL	mailbox	VARCHAR	255	FALSE	-
ENABLE	Enable or not 1 - Enable 0 - Do not enable	BOOLEAN	0	FALSE	-
LANGUAGE	language	VARCHAR	255	FALSE	-
LASTOPERATIONTYPE	Last modification type 1 - Manual modification 2 - Synchronous modification	INTEGER	32	TRUE	-
MALE	Gender 1 - male 0 - female	BOOLEAN	0	FALSE	-
MOBILE	cell-phone number	VARCHAR	255	FALSE	-
PASSWORD	password	VARCHAR	255	TRUE	The value of this field is the encrypted password of the platform user, which does not affect the login data decision system of the platform user
REALNAME	full name	VARCHAR	255	FALSE	-
USERNAME	user name	VARCHAR	255	TRUE	Associated table fields fine_base_message>userName fine_workflow_task>creatorName fine_schedule_record>creator fine_schedule_task>creator
WORKPHONE	cell-phone number	VARCHAR	255	FALSE	-
REALALIAS	RealName sort index	VARCHAR	255	FALSE	FR: 2019-12-05 and later jars, new fields BI: January 15, 2020 and later jars, new fields
USERALIAS	User name sort index	VARCHAR	255	FALSE	FR: 2019-12-05 and later jars, new fields BI: January 15, 2020 and later jars, new fields

2.2 FINE_EXTRA_Property user additional information table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
NAME	Property name	VARCHAR	255	TRUE	-
RELATEDID	User ID	VARCHAR	255	TRUE	Associated table fields fine_user>id
TYPE	The type of data item associated with	INTEGER	32	TRUE	-
VALUE	Property value	VARCHAR	65536	FALSE	-

2.3 FINE_Department table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_dep_role>departmentId
CREATIONTYPE	build type 1 - Create manually 2 - Synchronous creation	INTEGER	32	TRUE	-
DESCRIPTION	describe	VARCHAR	1000	FALSE	-
ENABLE	Enable or not 1 - Enable 0 - Do not enable	BOOLEAN	0	FALSE	-
LASTOPERATIONTYPE	Last modification type 1 - Manual modification 2 - Synchronous modification	INTEGER	32	TRUE	-
NAME	Department name	VARCHAR	255	FALSE	-
PARENTID	Parent department ID	VARCHAR	255	FALSE	-
FULLPATH	Complete path of Department Grandfather Department ID Parent department ID ...	VARCHAR	65536	FALSE	Fr: jar after May 20, 2019, new field Bi: June 13, 2019 and later jars, new fields
ALIAS	Sort index	VARCHAR	255	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: 2010-01-15 and later jars, new fields

2.4 FINE_Post position table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_dep_role>postId
CREATIONTYPE	build type 1 - Create manually 2 - Synchronous creation	INTEGER	32	TRUE	-
DESCRIPTION	describe	VARCHAR	1000	FALSE	-
ENABLE	Enable or not 0 - Do not enable 1 - Enable	BOOLEAN	0	FALSE	-
LASTOPERATIONTYPE	Last modification type 1 - Manual modification 2 - Synchronous modification	INTEGER	32	TRUE	-
NAME	Title of position	VARCHAR	255	FALSE	-
ALIAS	Sort index	VARCHAR	255	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields

2.5 FINE_DEP_Middle table of roles in role Department

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_user_role_middle>roleId
CREATIONTYPE	build type 1 - Create manually 2 - Synchronous creation	INTEGER	32	TRUE	-
DEPARTMENTID	Last modification type 1 - Manual modification 2 - Synchronous modification	VARCHAR	255	TRUE	-
LASTOPERATIONTYPE	Associated department and job ID Departmentid is empty, postid is empty: all department roles of built-in + synchronous Department (not visible at the front desk) Departmentid is empty, postid is not empty: does not exist Departmentid is not empty, postid is empty: Department roles that do not contain jobs Departmentid is not empty, postid is not empty: indicates the normal department job role	INTEGER	32	TRUE	Associated table fields fine_department>id
POSTID	VARCHAR	255	TRUE	Associated table fields fine_post>id
FULLPATH	Complete path of intermediate data	VARCHAR	65536	FALSE	Fr: jar after May 20, 2019, new field Bi: June 13, 2019 and later jars, new fields

2.6 FINE_CUSTOM_Role custom role table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_user_role_middle>roleId
CREATIONTYPE	build type 1 - Created manually by administrator 2 - Synchronous dataset creation	INTEGER	32	TRUE	-
DESCRIPTION	Description information	VARCHAR	255	FALSE	-
ENABLE	Enable or not 1 - Enable 0 - Do not enable	BOOLEAN	0	FALSE	-
LASTOPERATIONTYPE	Last modification type 1 - Manual modification 2 - Synchronous modification	INTEGER	32	TRUE	-
NAME	Role name	VARCHAR	255	FALSE	-
ALIAS	Sort field index	VARCHAR	255	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields

2.7 FINE_USER_ROLE_Middle user role table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
ROLEID	Associated generalized role ID Deproleid or customroleid	VARCHAR	255	TRUE	Associated table fields fine_dep_role>id fine_custom_role>id fine_authority>roleId
ROLETYPE	The type of generalized role associated with 1 - Department position 2 - Custom roles	INTEGER	32	TRUE	-
USERID	Associated user ID	VARCHAR	255	TRUE	Associated table fields fine_user>id

3. Permissions directory

3.1 FINE_Authority table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
AUTHORITY	Permission value 1 - refuse 2 - allow	INTEGER	32	TRUE	-
AUTHORITYENTITYID	Associated permission entity ID	VARCHAR	255	TRUE	-
AUTHORITYENTITYTYPE	The type of permission entity associated with Platform type 0 - Directory permissions, management system permissions and entities are all in authority_In the object table 1 - Personnel management - Department authority, personnel management - role authority 2 - Data connection permission 7 - Scheduled scheduling authority Report type 101 - finereport template permissions (template authentication) BItype 201 - Bi business package permissions 202 - Bi service package line filter permission (* not perceived by the outside world) 203 - Bi dashboard permissions (mainly for sharing) 204 - Bi template permissions (template authentication) 205 - Bi dashboard share control (role to role)	INTEGER	32	TRUE	-
AUTHORITYTYPE	Permission type Platform type 1 - View permissions 2 - Authorized authority 3 - Edit permission 4 - Data connection management permission Report type 101 - finereport template authentication permission 102 - finereport template view permission 103 - filling authority of finereport template 104 - Batch import task permission BItype 201 - Business package permission 202 - Business package management authority 203 - Bi report export permission 204 - Bi dashboard sharing rights 205 - Bi template authentication permission 206 - Bi template view permission 207 - Bi template export permission 208 - Bi dashboard share role control rights 209 - Bi dashboard share function permission 210 - public link function permission of Bi dashboard	INTEGER	32	TRUE	-
ROLEID	The associated generalized role ID	VARCHAR	255	TRUE	Associated table fields fine_dep_role>id fine_custom_role>id fine_user_role_middle>id
ROLETYPE	The type of generalized role associated with 1 - Department, Department Post 2 - Custom roles 3 - user 4 - post	INTEGER	32	TRUE

3.2 FINE_AUTHORITY_Object permission entity table

Including directory information, management system

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
EXPANDID	Associated extended attribute record ID	VARCHAR	255	FALSE	-
EXPANDTYPE	The associated extended property type Platform type 1 - Platform management system node 2 - home page 3 - catalog 5 - link 6 - file Report type 101 - Reporting process 102 - FineReport Report BItype 201 - BI Report	INTEGER	32	FALSE	-
PARENTID	The associated parent node ID	VARCHAR	255	FALSE	-
COVERID	Cover ID Directory Cover in system management > appearance configuration > directory style	VARCHAR	255	FALSE	-
DESCRIPTION	Description information	VARCHAR	65536	FALSE	-
DEVICETYPE	Display type 0 - PC, tablet, mobile phone not checked 1 - PC 2 - Flat 4 - mobile phone 5 - Check PC, mobile phone 6 - Check tablet, mobile phone 7 - Check PC, tablet and mobile phone	INTEGER	32	FALSE	-
DISPLAYNAME	Displays the report name and directory name	VARCHAR	255	TRUE	-
ICON	Icon ID System Management > appearance configuration > directory icon in directory style	VARCHAR	255	FALSE	-
PATH	Different entry types have different meanings	VARCHAR	255	FALSE	-
SORTINDEX	Sort order	BIGINT	64	FALSE	-
MOBILEICON	Mobile icon ID	VARCHAR	255	FALSE	-
FULLPATH	Entity complete path	VARCHAR	65536	FALSE	Fr: jar after May 20, 2019, new field New fields after 06-2019 and jar-13

3.3 FINE_AUTH_Preference permission panel user preferences

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
AUTHTYPE	Permission panel type	INTEGER	32	FALSE	-
AUTHVISIBLECFG	Permission visibility configuration	BIGINT	64	FALSE	-
USERID	User ID	VARCHAR	255	FALSE	Associated table fields fine_user>id

3.4 FINE_HOMEPAGE_Expand home page extension table

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
ANDROIDPADHOMEPAGE	Home page link for Android Tablet	VARCHAR	1000	FALSE
ANDROIDPHONEHOMEPAGE	Home page links for Android Phones	VARCHAR	1000	FALSE
IPADHOMEPAGE	Home page link for iPad	VARCHAR	1000	FALSE
IPHONEHOMEPAGE	Home page link for iPhone	VARCHAR	1000	FALSE
PCHOMEPAGE	Home page link for PC	VARCHAR	1000	FALSE
TYPE	Home page type 0 - finereport template 1 - Platform directory 2 - link 3 - FineBI template	INTEGER	32	FALSE

3.5 FINE_FAVORITE_Entry collection node table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
ENTRYID	Favorite report ID	VARCHAR	255	FALSE	-
TIME	Collection time	TIMESTAMP	26	FALSE	-
USERID	User ID collection	VARCHAR	255	FALSE	Associated table fields fine_user>id

4. Sign in

4.1 FINE_LAST_Login last login information table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
CITY	Log in to your city	VARCHAR	255	FALSE	-
IP	Login IP	VARCHAR	255	FALSE	-
TIME	login time	TIMESTAMP	26	FALSE	-
USERID	Login user ID	VARCHAR	255	FALSE	Associated table fields fine_user>id

4.2 FINE_LOGIN_Lock login lock table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
ERRORTIME	Number of password errors	INTEGER	32	FALSE	-
LOCKOBJECT	Lock IP or username	VARCHAR	255	FALSE	-
LOCKOBJECTVALUE	The value of IP or username	VARCHAR	255	FALSE	-
LOCKTIME	When is it locked	TIMESTAMP	26	FALSE	-
LOCKED	Usually empty	BOOLEAN	0	FALSE	-
UNLOCKTIME	When to unlock	TIMESTAMP	26	FALSE	-
USERID	User ID	VARCHAR	255	FALSE	Associated table fields fine_user>id

4.3 FINE_BLOCK_IP login lock IP table

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
CREATETIME	Lock time	TIMESTAMP	26	FALSE
IP	Locked IP	VARCHAR	255	FALSE
REJECTEDVISITS	Rejection times	INTEGER	32	FALSE

5. Backup restore

5.1 FINE_BACKUP_Node backup node table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
BACKUPMODULE	Backup module Jar: jar package jar-cluster：jar package in cluster (it is special, in cluster, the backup of jar package will be automatically converted to proxy implementation, so separate this module.) Plugins: plugins Dashboards: BI template reportlets: Report template Config: platform configuration	VARCHAR	255	FALSE	-
BACKUPNAME	Backup name	VARCHAR	255	FALSE	-
BACKUPTIME	When to back up	TIMESTAMP	26	FALSE	-
SAVEPATH	Backup address	VARCHAR	1000	FALSE	-
BACKUPSIZE	Backup file size	DOUBLE	64	FALSE	-
TYPE	type Auto: automatic backup Manual: automatic backup	VARCHAR	255	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields

6. Scheduled scheduling

6.1 FINE_SCHEDULE_Task timing task table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_schedule_task_param>taskId fine_schedule_record>taskId
BACKUPFILEPATH	Backup file path	VARCHAR	1000	FALSE	Reserved field, not used
CREATOR	Task Creator	VARCHAR	255	FALSE	Associated table fields fine_user>userName fine_schedule_record>creator
EDITABLE	Can the task be edited	BOOLEAN	0	FALSE	Reserved field, not used
FILECLEARCOUNT	Number of attachment cleanups -1 - Do not clean up 0 - Clean up at the end of the task 1 - Do not clean up Other positive integers - reserved times	INTEGER	32	FALSE	-
NEXTFIRETIME	Next execution time yyyy-MM-dd HH:mm:ss	TIMESTAMP	26	FALSE	-
OUTPUTSTR	Task attachment processing type combination string, used for filtering condition query File processing, separated by commas: 1 - Email notification 2 - FTP upload attachment 3 - platform notification 5 - SMS notification 6 - Mount platform 7 - Custom attachment processing 8 - print file 9 - client notification 10 - SFTP upload	VARCHAR	1000	FALSE	-
PREFIRETIME	Last execution time yyyy-MM-dd HH:mm:ss	TIMESTAMP	26	FALSE	-
REPEATTIME	Repeat interval	INTEGER	32	FALSE	-
REPEATTIMES	Repeat times	INTEGER	32	FALSE	-
SENDBACKUPFILE	Send backup file	BOOLEAN	0	FALSE	Reserved field, not used
SHOWTYPE	Display type 0 - Pagination Preview 1 - Report Preview 2 - Data analysis Preview 3 - Form Preview 4 - New report	INTEGER	32	FALSE	-
TASKCONDITION	Task status JSON format, including type and description. type: 0 - Always implement 1 - Formula judgment 2 - User defined class judgment description: Specific content (specific formula or class name)	VARCHAR	255	FALSE	-
TASKDESCRIPTION	Task description	VARCHAR	1000	FALSE	Reserved field, not used
TASKNAME	Task name	VARCHAR	255	TRUE	-
TASKPARAMETER	Task parameters JSON form, including inputstyle parameter input method, name parameter name, type parameter type, value parameter value inputStyleInput mode (not required) 0 - default 1 - data set typeParameter type String Integer Double Date Boolean Tablecolumn valueParameter value If the parameter input method is the default, the value is a string If the parameter input method is dataset, the value data set name and colname dataset field value are included	VARCHAR	65536	FALSE	-
TASKSTATE	Task status In operation, pause and end do not necessarily correspond to the status of the foreground display, which needs to be calculated before the display to the foreground	INTEGER	32	FALSE	-
TASKTYPE	Task type 0 - No scheduling object 1 - Report template 2 - BI template	INTEGER	32	FALSE	-
TEMPLATEPATH	Template path	VARCHAR	1000	TRUE	-
TRIGGERGROUP	Trigger group JSON form, including multiple triggers, including trigger type, time, etc triggerTypeTrigger type: 1 - Only once 2 - Simple repeat 3 - Detail frequency setting 4 - Expression settings startTimeStart time: yyyy-MM-dd HH:mm:ss startTypeStart type: 1 - Immediately 2 - Select start time endTypeEnd type: 1 - End immediately after execution 2 - No time limit 3 - Select end time 4 - How many extra runs recurrenceIntervalSimple repeat interval (not required) recurrenceIntervalUnitSimple repeat interval time unit (not required) 1 - minute 2 - hour 3 - day 4 - week repeatCountAdditional execution times (not required) integer hoursDetailed frequency execution hours (not required) integer minutesDetailed frequency execution minutes (not required) integer dayTypeDetailed frequency execution date (not required) 1 - everyday 2 - weekly 3 - monthly monthDaysWhen the execution date of the detailed frequency is monthly, select the specific days of each month (not required) Integer array weekDaysWhen the execution day of the detailed frequency is weekly, select the specific days of each week (not required) Integer array monthsWhen the detailed frequency is implemented, which months (not required) should be implemented Integer array	VARCHAR	65536	FALSE	-
USERGROUP	User group JSON form: Customrole role role list: role ID array Customrolestr role list string: for foreground display Department and post Department list: Department ID array Departmentstr Department list string: used for foreground display Platformuser user list (not required): array in the format of "name (user name)" Platformuserstr user list string (not required): for foreground display User type: 1 - platform user, 2 - custom user Columnindex custom user - data set column number (not required) Columnindexstr custom user - dataset column name (not required) Tabledataname custom user - dataset name (not required)	VARCHAR	65536	FALSE	-
SCHEDULEOUTPUT	Task push	VARCHAR	255	FALSE	Associated table fields fine_schedule_output>id
CONDITIONPARAMETER	Custom class parameters for execution conditions JSON form: Name parameter name Value parameter value	VARCHAR	1000	FALSE	2020-06-08 And after the jar, new fields

6.2 FINE_SCHEDULE_TASK_Param scheduled task parameter values

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
PARAM	parameter list JSON form: Parameter name: parameter value	VARCHAR	65536	FALSE	-
TASKNAME	Task name	VARCHAR	255	FALSE	-
TASKID	Task ID	VARCHAR	255	FALSE	Associated table fields fine_schedule_task>id

6.3 FINE_SCHEDULE_Record scheduled task execution log

Note: for projects before May 20, 2019, fine is used_schedule_The record table stores the scheduled task execution log

For the project of jar package on May 20, 2019 and after, fine in Logdb database is used_schedule_The record table stores the scheduled task execution log. Please refer to the report log Logdb database

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
CREATOR	creator	VARCHAR	255	FALSE	-
DETAILMESSAGE	detailed information	VARCHAR	65536	FALSE	-
FILEPATH	Generate attachment path	VARCHAR	1000	FALSE	Reserved field, not used
LOGMESSAGE	log information	VARCHAR	255	FALSE	-
LOGTIME	Task execution time Log printing time	TIMESTAMP	26	FALSE	-
LOGTYPE	Log type 0-fail 1-success 2-skip	INTEGER	32	FALSE	-
NEXTFIRETIME	Next record time	TIMESTAMP	26	FALSE	Reserved field, not used
RUNTYPE	Attachment processing type 0 - Snapshot generation 1 - Mail sending 2 - FTP upload 3 - Platform message push 4 - Document printing 5 - SMS sending 6 - Mounting platform 7 - Custom class processing 8 - Fill in regularly 9 - client notification 10 - SFTP upload -1 - Attachment sending (default)	INTEGER	32	FALSE	-
TASKNAME	Task name	VARCHAR	255	TRUE	-
TASKID	Task ID	VARCHAR	255	FALSE	Associated table fields fine_schedule_task>id

6.4 FINE_SCHEDULE_Export in output timing task

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_schedule_task>scheduleOutput fine_base_output>output_Id
BASENAME	Generate attachment name	VARCHAR	65536	FALSE	-
CREATEATTACHBYUSERNAME	Do you want to generate different attachments by different users 1 - yes 0 - no	BOOLEAN	0	FALSE	-
FORMATS	Export attachment type JSON format: formatnum file processing method: 0 - Output CPR 1 - Output new version of Excel 2 - Output PDF 4 - Output word 8 - Output old version of Excel 16 - Output png 32 - Output FRR	VARCHAR	255	FALSE	-

6.5 FINE_BASE_Output task attachment processing main table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
ACTIONNAME	Attachment processing class name	VARCHAR	255	TRUE
EXECUTEBYUSER	Do you want to execute separately by different users 1 - yes 0 - no	BOOLEAN	0	TRUE
RESULTURL	Results link	VARCHAR	1000	FALSE
RUNTYPE	Attachment processing type 0 - Snapshot generation 1 - Mail sending 2 - FTP upload 3 - Platform message push 4 - Document printing 5 - SMS sending 6 - Mounting platform 7 - Custom class processing 8 - Fill in regularly 9 - client notification 10 - SFTP upload -1 - Attachment sending (default)	INTEGER	32	TRUE
OUTPUTID	Export ID	VARCHAR	255	FALSE	Associated table fields fine_schedule_output>id

6.6 FINE_OUTPUT_Class custom class processing

Field name

describe

data type

length

Not empty

remarks

CLASSNAME

Custom class name

VARCHAR

255

FALSE

Primary key

VARCHAR

255

TRUE

Associated table fields

fine_base_output>id

6.7 FINE_OUTPUT_CLIENT_Note client notification table

Field name	describe	data type	length	Not empty	remarks
ADDRESSEE	Receiver	VARCHAR	65536	FALSE
CONTENT	content	VARCHAR	65536	FALSE
CUSTOMIZELINK	Custom link	VARCHAR	65536	FALSE
LINKOPENTYPE	Link type 1 - Timing results link 2 - Custom link	INTEGER	32	FALSE
MEDIAID	The image ID of the rich text message	VARCHAR	255	FALSE
SUBJECT	theme	VARCHAR	65536	FALSE
TERMINAL	Push terminal At present, it is fixed to 1, representing app notification	INTEGER	32	FALSE
TYPE	Message type 1 - Link message 2 - Graphic message 3 - File message	INTEGER	32	FALSE
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id

6.8 FINE_OUTPUT_Email push mail table

Field name	describe	data type	length	Not empty	remarks
ADDLINK	Results link	BOOLEAN	0	FALSE	-
BCCADDRESS	bcc	VARCHAR	65536	FALSE	-
BODYCONTENT	content	VARCHAR	65536	FALSE	-
CCADDRESS	CC	VARCHAR	65536	FALSE	-
PREVIEWATTACH	Text Preview	BOOLEAN	0	FALSE	-
SUBJECT	theme	VARCHAR	65536	FALSE	-
USEATTACH	Using accessories	BOOLEAN	0	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id
CUSTOMADDRESS	-	VARCHAR	1000	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields
CUSTOMBCCADDRESS	-	VARCHAR	1000	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields
CUSTOMCCADDRESS	-	VARCHAR	1000	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields

6.9 FINE_OUTPUT_FTP upload table

Field name	describe	data type	length	Not empty	remarks
PASSWORD	password	VARCHAR	255	FALSE	-
PORT	Port number	VARCHAR	255	FALSE	-
SAVEPATH	Upload path	VARCHAR	255	FALSE	-
SERVERADDRESS	server address	VARCHAR	255	FALSE	-
USERNAME	user name	VARCHAR	255	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id
FTPMODE	FTP mode Passive: passive mode Active: active mode	VARCHAR	255	FALSE	-

6.10 FINE_OUTPUT_Mount scheduled task mount directory

Field name	describe	data type	length	Not empty	remarks
DESCRIPTION	describe	VARCHAR	65536	FALSE	-
FOLDERENTRYID	Mount directory ID	VARCHAR	255	FALSE	-
FOLDERENTRYNAME	Mount directory name	VARCHAR	255	FALSE	-
FOLDERENTRYSTR	Mount directory	VARCHAR	255	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id

6.11 FINE_OUTPUT_PLATFORM_MSG platform system message

Field name	describe	data type	length	Not empty	remarks
CONTENT	content	VARCHAR	65536	FALSE	-
LINKOPENTYPE	Link type 1 - Timing results link 2 - Custom link	INTEGER	32	FALSE	-
SUBJECT	theme	VARCHAR	65536	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id

6.12 FINE_OUTPUT_Print processing

Field name

describe

data type

length

Not empty

remarks

PRINTERNAME

Printer name

VARCHAR

255

FALSE

Primary key

VARCHAR

255

TRUE

Associated table fields

fine_base_output>id

6.13 FINE_OUTPUT_SFTP SFTP upload table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id
PASSWORD	password	VARCHAR	255	FALSE	-
PORT	Port number	VARCHAR	255	FALSE	-
PRIVATEKEY	Private key	VARCHAR	255	FALSE	-
SAVEPATH	Upload path	VARCHAR	255	FALSE	-
SERVERADDRESS	server address	VARCHAR	255	FALSE	-
USERNAME	user name	VARCHAR	255	FALSE	-

6.14 FINE_OUTPUT_SMS message sending

Field name	describe	data type	length	Not empty	remarks
TEMPLATEID	Template ID	INTEGER	32	FALSE
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_output>id
SMSPARAM	SMS parameters JSON, for each parameter: ID parameter Idname parameter name Value parameter value Type parameter type typeTypes include: String - string Integer - integer Double - Double Date - date Boolean - Boolean Formula - formula	VARCHAR	255	FALSE	Fr: 2019-12-05 and later jars, new fields Bi: January 15, 2020 and later jars, new fields

7. news

7.1 FINE_BASE_Message basic message table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
CREATETIME	Message creation time	TIMESTAMP	26	FALSE
DATETIME	Message time	TIMESTAMP	26	FALSE	newly added
MESSAGE	Message content	VARCHAR	65536	FALSE
READED	Read or not 1 - yes 0 - no	BOOLEAN	0	FALSE
TOASTED	Has the pop-up prompt been displayed 1 - yes 0 - no	BOOLEAN	0	FALSE
TYPE	Message type 0 - System message 1 - Report the news 2 - Template message 3 - Mobile message -1 - Unknown message	INTEGER	32	FALSE
URL	URL	VARCHAR	1000	FALSE
URLTYPE	URL type 0 - nothing 1 - Internal link type, such as / report / entry / {ID} 2 - External link types, such aswww.fanruan.com 3 - Platform block routing, jump to a tab page of system management 4 - Open the URL of multiple templates in the platform	INTEGER	32	FALSE
USERID	User ID	VARCHAR	255	FALSE	Associated table fields fine_user>id
USERNAME	user name	VARCHAR	255	FALSE	Associated table fields fine_user>userName

7.2 FINE_PROCESS_Message push message table

Field name	describe	data type	length	Not empty	remarks
ALLTASKID	All task IDS	VARCHAR	255	FALSE	-
DEADLINE	End time	TIMESTAMP	26	FALSE	-
PROCESSED	Is it complete 1-complete 0-hang in the air	BOOLEAN	0	FALSE	-
TASKID	Report task ID	VARCHAR	255	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_message>id

7.3 FINE_SYSTEM_Message table of message system

Field name	describe	data type	length	Not empty	remarks
TERMINAL	Push terminal At present, it is fixed to 1, which represents the message notification of PC	BIGINT	64	FALSE	-
TITLE	theme	VARCHAR	255	FALSE	-
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_base_message>id

8. Report

Note: for jars after December 27, 2018, a new report related form is added.

8.1 FINE_Flow chart in workflow reporting

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
CREATETIME	Creation time	TIMESTAMP	26	FALSE	-
CREATORID	Creator ID	VARCHAR	255	FALSE	Associated table fields fine_workflow_task>creatorId fine_workflow_stash_data>userId fine_workflow_log>operatorname
DESCRIPTION	describe	VARCHAR	65536	FALSE	-
NAME	Process name	VARCHAR	255	FALSE	-
NODESID	ID node	VARCHAR	65536	FALSE	Associated table fields fine_workflow_node>id

8.2 FINE_WORKFLOW_Task report process task table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_workflow_task_impl>taskId
CREATETIME	Creation time	TIMESTAMP	26	FALSE
CREATORID	Creator ID	VARCHAR	255	FALSE	Associated table fields fine_user>id fine_workflow>creatorId
CREATORNAME	Name of Creator	VARCHAR	255	FALSE	Associated table fields fine_user>username
DEADLINEDATE	deadline	INTEGER	32	FALSE
DEADLINETYPE	Cut off type	VARCHAR	255	FALSE
ISSUECONTROL	Regular distribution	VARCHAR	65536	FALSE
ISSUEOVER	End of distribution 1 - yes 0 - no	BOOLEAN	0	FALSE
LEAPFROGBACK	Step back	BOOLEAN	0	FALSE
NAME	Task name	VARCHAR	255	FALSE
PARENTID	Parent task ID	VARCHAR	255	FALSE	Associated table fields fine_workflow_task_impl>parentId
PROCESSID	Process ID	VARCHAR	255	FALSE	Associated table fields fine_workflow_task_impl>processId
REMINDCONTROL	Reminders	VARCHAR	65536	FALSE
TASKNAMECALCULATEONCE	Check "calculate only once when task is initiated" when adding task 1 - Check 2 - Not checked	BOOLEAN	0	FALSE

8.3 FINE_WORKFLOW_TASK_Impl specific task list

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
ALERTED	Early warning or not 1 - yes 0 - no	BOOLEAN	0	FALSE
COMPLETESTATE	The operator and completion status of the current task, 1 - Completed 0 - hang in the air For example: {"demo / authority / product sales query. CPT": {"Sunlin": 0}}	VARCHAR	65536	FALSE
CREATETIME	Creation time (time of distribution)	TIMESTAMP	26	FALSE
CURRENTNODEIDX	Current process node ID	INTEGER	32	FALSE
DEADLINE	deadline	TIMESTAMP	26	FALSE
FRTASKID	ID of the source task	VARCHAR	255	FALSE
NAME	Task name	VARCHAR	255	FALSE
NEEDALLCOMPLETE	Do you need to complete all of them 1 - yes 0 - no	BOOLEAN	0	FALSE
NODEROUTE	The path of the node json	VARCHAR	65536	FALSE
NOTE	remarks	VARCHAR	16777216	FALSE
OPERATORJSON	Which node on node is multiuser	VARCHAR	65536	FALSE
OPERATOROFFSET	The number of users in a multiuser node	VARCHAR	65536	FALSE
OPERATOROFFSETNAME	The name of the user in the multiuser node	VARCHAR	65536	FALSE
PARENTID	Parent task ID	VARCHAR	255	FALSE	Associated table fields fine_workflow_task>parentId
PROCESSID	Process ID	VARCHAR	255	FALSE	Associated table fields fine_workflow_task>processId
REPORTOFFSET	How many templates	INTEGER	32	FALSE
SENDTIME	Sending time	TIMESTAMP	26	FALSE
SENDER	Sender	VARCHAR	255	FALSE
SENDERID	Sender ID	VARCHAR	255	FALSE
SONTASKID	The ID of the subtask [nodeIdx:0,userId:1, taskId:1]	VARCHAR	255	FALSE
STATE	Task status -1 - initial 0 - Waiting for report 1 - Waiting for review 2 - Approved 3 - Returned 4 - It's closed 5 - overtime	INTEGER	32	FALSE
TASKID	ID of the source task	VARCHAR	255	FALSE	Associated table fields fine_workflow_task>Id

8.4 FINE_WORKFLOW_Node report process node table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	Associated table fields fine_workflow>nodesId
ALERTCONTROL	Alert details	VARCHAR	1000	FALSE
AUTHORITY	jurisdiction	VARCHAR	255	FALSE
DESCRIPTION	describe	VARCHAR	1000	FALSE
NAME	Node name	VARCHAR	255	FALSE
NEEDALLCOMPLETE	Do you need to complete the transfer 1 - yes 0 - no	BOOLEAN	0	FALSE
NEEDOFFLINEREPORT	Do you need to fill in offline 1 - yes 0 - no	BOOLEAN	0	FALSE
PROCESSID	Process ID	VARCHAR	255	FALSE
REPORTCONTROL	Detailed information reporting	VARCHAR	1000	FALSE

8.5 FINE_WORKFLOW_STASH_Data report process data temporary storage table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
DATA	data	VARCHAR	16777216	FALSE
REPORTPATH	Report path	VARCHAR	65536	FALSE
USERID	User ID	VARCHAR	255	FALSE	Associated table fields fine_workflow>creatorId
TASKID	Task ID	VARCHAR	255	FALSE

8.6 FINE_WORKFLOW_Log report process operation log

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
DATETIME	time	TIMESTAMP	26	FALSE
MESSAGE	news	VARCHAR	65536	FALSE
OPERATORNAME	Operator Name	VARCHAR	255	FALSE	Associated table fields fine_workflow>creatorId
PROCESSNAME	Process name	VARCHAR	255	FALSE
TASKNAME	Task name	VARCHAR	255	FALSE

9. system configuration

9.1 FINE_CONF_Classname interface configuration type table

Field name	describe	data type	length	Not empty
ID	The position of the current field in the configuration	VARCHAR	255	TRUE
CLASSNAME	The field type of the corresponding configuration value in the configuration	VARCHAR	255	FALSE

9.2 FINE_CONF_Entity configuration class data table

Field name	describe	data type	length	Not empty
ID	Location of data in configuration	VARCHAR	255	TRUE
VALUE	Data value	VARCHAR	65536	FALSE

Note 1: most of the configuration contents stored in the database are in this table, such as ID=BackupConfig.backupMemory , value = 1024 indicates that a value of 1024 is configured for backupmemory in backupconfig, which means that automatic backup takes up 1024MB at most.

The common configuration items of the platform and the foreground do not provide the configuration interface, and they are basically stored in fine_conf_In the entity table, see configuration information storage table for details

9.3 FINE_CONF_Configuration corresponding table of XML entity XML storage

Field name	describe	data type	length	Not empty
ID	Location of data in configuration	VARCHAR	255	TRUE
VALUE	The XML text value of the field	BLOB	67108864	FALSE

9.4 fine_International multi language support internationalization data table

Note: this table appears in the finereport version of jar package on February 28, 2020 and later.

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE	-
DESCRIPTION	describe	VARCHAR	1000	FALSE	-
I18NKEY	International key	VARCHAR	255	FALSE	-
LANGUAGE	International language Zh_Cn: Simplified Chinese Zh_Tw: Traditional Chinese en_ Us: English Ja_JP: Japanese Ko_Kr: Korean	VARCHAR	255	FALSE	-
I18NVALUE	The value of internationalization	VARCHAR	1000	FALSE	Chinese characters need to be converted to unicode by online conversion tool before writing

10. Swift module (modification not allowed)

10.1 FINE_SWIFT_COL_IDX_Conf field index configuration table

Field name	describe	data type	length	Not empty
COLUMNNAME	Field name	VARCHAR	255	TRUE
TABLEKEY	Datasheet sourcekey	VARCHAR	255	TRUE
REQUIREGLOBALDICT	Generate global index 1 - yes 0 - no	BOOLEAN	0	FALSE
REQUIREINDEX	Generate index 1 - yes 0 - no	BOOLEAN	0	FALSE

10.2 FINE_SWIFT_CONFIG_Entity swift internal configuration table

Field name	describe	data type	length	Not empty
CONFIGKEY	Configuration location	VARCHAR	255	TRUE
CONFIGVALUE	Configuration value	VARCHAR	65536	FALSE

10.3 FINE_SWIFT_Metadata data table metadata storage table

Field name	describe	data type	length	Not empty
ID	Sourcekey calculated from data table	VARCHAR	255	TRUE
FIELDS	Field information	VARCHAR	65536	FALSE
REMARK	Transliteration	VARCHAR	255	FALSE
SCHEMANAME	Schema of database table	VARCHAR	255	FALSE
SWIFTSCHEMA	Storage location of data files CUBE / LOG	VARCHAR	255	FALSE
TABLENAME	Table name	VARCHAR	255	FALSE

10.4 FINE_SWIFT_SEG_Location swift segment distribution information

Field name	describe	data type	length	Not empty
CLUSTERID	Cluster ID	VARCHAR	255	TRUE
SEGMENTID	Generated segment ID	VARCHAR	255	TRUE
SOURCEKEY	The data table sourcekey indicates which table segment belongs to	VARCHAR	255	FALSE

10.5 FINE_SWIFT_Segments swift segment details

Field name	describe	data type	length	Not empty
ID	Generated segment ID	VARCHAR	255	TRUE
SEGMENTORDER	Segment serial number	INTEGER	32	FALSE
SEGMENTOWNER	The data table sourcekey indicates which table segment belongs to	VARCHAR	255	FALSE
SEGMENTURI	The relative URL of the data file	VARCHAR	65536	FALSE
STORETYPE	Data saving type Memory - memory storage, only in memory, shutdown will be lost NiO - is to write the contents of memory to a file to solve the problem of shutdown loss FINE_IO - fr own implementation of an IO framework, NiO file full to fine_It's in io	VARCHAR	255	FALSE
SWIFTSCHEMA	Storage directory of data files CUBE / LOG	VARCHAR	255	FALSE

10.6 FINE_SWIFT_SERVICE_Info to save swift service information

Field name	describe	data type	length	Not empty
ID	Service ID	VARCHAR	255	TRUE
CLUSTER_ID	Cluster ID	VARCHAR	255	FALSE
IS_SINGLETON	Do you want to start only one 1 - yes 0 - no	BOOLEAN	0	FALSE
SERVICE	Service type cluster_master_Service - record the ID of the master node for all nodes to use synchronously. Other - services started by each node (such as query, import, history, real-time, etc.)	VARCHAR	255	FALSE
SERVICE_INFO	Other information about the service	VARCHAR	255	FALSE

10.7 FINE_SWIFT_TAB_IDX_Conf table index configuration

Field name	describe	data type	length	Not empty
TABLEKEY	Table sourcekey	VARCHAR	255	TRUE
ALLOTRULE	Block logic	VARCHAR	255	FALSE

10.8 FINE_SWIFT_TABLE_Path cube intermediate directory configuration management

Field name	describe	data type	length	Not empty
CLUSTERID	Cluster ID The single machine is local	VARCHAR	255	TRUE
TABLEKEY	Table sourcekey	VARCHAR	255	TRUE
LASTPATH	Last used temporary directory	INTEGER	32	FALSE
TABLEPATH	Intermediate directory currently used	INTEGER	32	FALSE
TMPDIR	Intermediate directory for cube generation	INTEGER	32	FALSE

11. Quartz module (modification not allowed)

11.1 QRTZ_BLOB_Triggers trigger stored in blob type

As a blob type storage, it is used for quartz users to create their own custom trigger type using JDBC, when jobstore does not know how to store instances.

Field name	describe	data type	length	Not empty
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	qrtz_Triggers table triggers_Foreign key of group	VARCHAR	255	TRUE
TRIGGER_NAME	qrtz_Triggers table triggers_Foreign key of name	VARCHAR	255	TRUE
BLOB_DATA	A BLOB field to store persistent trigger objects	VARBINARY	16777216	FALSE

11.2 QRTZ_Calendars calendar information storage table

Blob type is used to store calendar information. Quartz can configure a calendar to specify a time range.

Field name	describe	data type	length	Not empty
CALENDAR_NAME	Calendar name	VARCHAR	255	TRUE
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
CALENDAR	A blob is used to store the object calendar	VARBINARY	4000	FALSE

11.3 QRTZ_CRON_Triggers stores the trigger of cron type

The cron expression table that stores triggers.

Field name	describe	data type	length	Not empty
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	qrtz_Triggers table triggers_Foreign key of group	VARCHAR	255	TRUE
TRIGGER_NAME	qrtz_Triggers table triggers_Foreign key of name	VARCHAR	255	TRUE
CRON_EXPRESSION	Cron expression	VARCHAR	255	TRUE
TIME_ZONE_ID	time zone	VARCHAR	255	FALSE

11.4 QRTZ_FIRED_Triggers stores triggered triggers

The status information associated with the triggered job and the triggered job.

Field name	describe	data type	length	Not empty
ENTRY_ID	Scheduler instance ID	VARCHAR	255	TRUE
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
FIRED_TIME	Trigger time	NUMERIC	19	TRUE
INSTANCE_NAME	Scheduler instance name	VARCHAR	255	TRUE
IS_NONCONCURRENT	Concurrent 1 - yes 0 - no	BOOLEAN	0	TRUE
JOB_GROUP	The name of the group to which the job belongs in the cluster	VARCHAR	255	FALSE
JOB_NAME	The name of the job in the cluster	VARCHAR	255	FALSE
PRIORITY	priority	INTEGER	32	FALSE
REQUESTS_RECOVERY	Whether to accept recovery execution or not. The default value is 0 1 - yes 0 - no	BOOLEAN	0	TRUE
SCHED_TIME	Timer set time	NUMERIC	19	TRUE
STATE	state	VARCHAR	255	TRUE
TRIGGER_GROUP	qrtz_Triggers table triggers_Foreign key of group	VARCHAR	255	TRUE
TRIGGER_NAME	qrtz_Triggers table triggers_Foreign key of name	VARCHAR	255	TRUE

11.5 QRTZ_JOB_Details stores a job detail

Store the details of each configured job detail.

Field name	describe	data type	length	Not empty
JOB_GROUP	The name of the group to which the job belongs in the cluster	VARCHAR	255	TRUE
JOB_NAME	The name of the job in the cluster	VARCHAR	255	TRUE
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
DESCRIPTION	The fully qualified name of a notejob implementation class in the cluster. Quartz finds the job class according to this path to classpath	VARCHAR	255	FALSE
IS_DURABLE	Is it persistent 1 - Yes, quartz will persist the job to the database 0 - no	BOOLEAN	0	TRUE
IS_NONCONCURRENT	Concurrent execution 1 - yes 0 - no	BOOLEAN	0	TRUE
IS_UPDATE_DATA	Update data 1 - yes 0 - no	BOOLEAN	0	TRUE
JOB_CLASS_NAME	In the cluster, notejob implements the fully qualified name of the class, and quartz finds the job class according to this path to classpath	VARCHAR	255	TRUE
JOB_DATA	A BLOB field to store persistent job objects	VARBINARY	16777216	FALSE
REQUESTS_RECOVERY	Whether to accept recovery execution or not. The default value is 0 1 - yes 0 - no	BOOLEAN	0	TRUE

11.6 QRTZ_Locks stores lock information

Store the pessimistic lock information of the program (if pessimistic lock is used).

Field name	describe	data type	length	Not empty
LOCK_NAME	Pessimistic lock name	VARCHAR	255	TRUE
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE

11.7 QRTZ_PAUSED_TRIGGER_GRPS

Stores information about the pending trigger group.

Field name	describe	data type	length	Not empty
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	qrtz_Triggers table triggers_Foreign key of group	VARCHAR	255	TRUE

11.8 QRTZ_SCHEDULER_STATE

Store the information of note instances in the cluster, and quartz will read the information of the table regularly to judge the current state of each instance in the cluster.

Field name	describe	data type	length	Not empty
INSTANCE_NAME	In the previous configuration fileorg.quartz.scheduler. instanceid configuration name, The field is written	VARCHAR	255	TRUE
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
CHECKIN_INTERVAL	Inspection interval	NUMERIC	19	TRUE
LAST_CHECKIN_TIME	Last inspection time	NUMERIC	19	TRUE

11.9 QRTZ_SIMPLE_Information of simple triggers

Store simple triggers, including the number of repetitions, intervals, and the number of triggers.

Field name	describe	data type	length	Not empty
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	Trigger group	VARCHAR	255	TRUE
TRIGGER_NAME	Trigger Name	VARCHAR	255	TRUE
REPEAT_COUNT	Statistics of repeated times	NUMERIC	19	TRUE
REPEAT_INTERVAL	Repeat interval	NUMERIC	19	TRUE
TIMES_TRIGGERED	Number of times triggered	NUMERIC	19	TRUE

11.10 QRTZ_SIMPROP_TRIGGERS

qrtz_simprop_Triggers store calendar interval trigger (similar to simpletrigger, which specifies the task trigger to be executed at a certain time interval from a certain time) and daily time interval trigger (which specifies the task trigger to be executed at a certain time interval within a certain time period of each day)

Field name	describe	data type	length	Not empty
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	qrtz_Triggers table triggers_Foreign key of group	VARCHAR	255	TRUE
TRIGGER_NAME	qrtz_Triggers table triggers_Foreign key of name	VARCHAR	255	TRUE
BOOL_PROP_1	The first parameter of trigger of boolean type	BOOLEAN	0	FALSE
BOOL_PROP_2	Second parameter of trigger of boolean type	BOOLEAN	0	FALSE
DEC_PROP_1	The first parameter of trigger of decimal type	NUMERIC	19	FALSE
DEC_PROP_2	The second parameter of trigger of decimal type	NUMERIC	19	FALSE
INT_PROP_1	The first parameter of trigger of type int	INTEGER	32	FALSE
INT_PROP_2	The second parameter of trigger of type int	INTEGER	32	FALSE
LONG_PROP_1	The first parameter of trigger of long type	NUMERIC	19	FALSE
LONG_PROP_2	The second parameter of trigger of long type	NUMERIC	19	FALSE
STR_PROP_1	The first parameter of trigger of type string	VARCHAR	255	FALSE
STR_PROP_2	The second parameter of trigger of type string	VARCHAR	255	FALSE
STR_PROP_3	The third parameter of trigger of string type	VARCHAR	255	FALSE

11.11 QRTZ_Basic information of triggers

Save the basic information of the trigger.

Note: after setting the user synchronization data set, in qrtz_"Trigger" is found in the triggers table_"Name" is the data of "syncuser". You can view the update time of users.

Field name	describe	data type	length	Not empty	remarks
SCHED_NAME	Dispatch name	VARCHAR	255	TRUE
TRIGGER_GROUP	Trigger group name	VARCHAR	255	TRUE
TRIGGER_NAME	Trigger Name	VARCHAR	255	TRUE
CALENDAR_NAME	Calendar name	VARCHAR	255	FALSE
DESCRIPTION	Detailed description information	VARCHAR	255	FALSE
END_TIME	End time	NUMERIC	19	TRUE
JOB_DATA	A BLOB field to store persistent job objects	VARBINARY	16777216	FALSE
JOB_GROUP	qrtz_job_Details table job_Foreign key of group	VARCHAR	255	TRUE
JOB_NAME	qrtz_job_Details table job_Foreign key of name	VARCHAR	255	TRUE
MISFIRE_INSTR	Measures or strategies of compensation implementation	INTEGER	32	FALSE
NEXT_FIRE_TIME	Next trigger time	NUMERIC	19	FALSE
PREV_FIRE_TIME	Last trigger time	NUMERIC	19	FALSE
PRIORITY	priority	INTEGER	32	FALSE
START_TIME	start time	NUMERIC	19	TRUE
TRIGGER_STATE	Current trigger state Waiting - waiting Pause - pause Requested - normal execution Blocked - blocked Error - error	VARCHAR	255	TRUE
TRIGGER_TYPE	The type of trigger Simple - repeat after a specific time interval.If it starts at 9 o'clock, it will be executed every 1 hour. Cron - based on calendar schedule, e.g. every Tuesday at 2am.	VARCHAR	255	TRUE
APPOINT_ID	Platform cluster node ID.Indicates which node the trigger needs to run on. If it is blank, it will be executed.	VARCHAR	255	FALSE	2020New in May

12. Mobile terminal

12.1 FINE_MOBILE_Device mobile device list

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
CREATEDATE	Device add date	TIMESTAMP	26	FALSE
DEVICENAME	Equipment name	VARCHAR	255	FALSE
MACADDRESS	Device MAC address	VARCHAR	255	FALSE
PASSED	Is the equipment certified 1 - yes 0 - no	BOOLEAN	0	FALSE
UPDATEDATE	Equipment modification date	TIMESTAMP	26	FALSE
USERNAME	Associated user name	VARCHAR	255	FALSE

12.2 FINE_MOBILE_PUSH_Message push table of mobile terminal

Field name	describe	data type	length	Not empty
GROUPID	Message receiving group ID	VARCHAR	255	FALSE
MEDIAID	The image ID of the rich text message	VARCHAR	255	FALSE
MSGTYPE	Message type 1 - Plain text message 2 - Graphic message 3 - File message	INTEGER	32	FALSE
TERMINAL	Push terminal At present, it is fixed to 1, representing app notification	INTEGER	32	FALSE
TITLE	Message title	VARCHAR	255	FALSE
ID	Primary key	VARCHAR	255	TRUE

13. report form

13.1 FINE_PARAM_Template parameter combination

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
TEMPLATEID	Template ID	VARCHAR	255	FALSE
TPGROUP	Parameter combination	VARCHAR	65536	FALSE
USERNAME	user name	VARCHAR	255	FALSE

13.2 FINE_PRINT_Offset printing offset

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
CPTNAME	Template name	VARCHAR	50	FALSE
IP	Client IP address	VARCHAR	20	FALSE
OFFSETX	Lateral offset	VARCHAR	50	FALSE
OFFSETY	Longitudinal offset	VARCHAR	50	FALSE
SIGN	Offset options 0 - No offset 1 - Global configuration 2 - Single template configuration	VARCHAR	10	FALSE

13.3 FINE_PRINT_OFFSET_IP_Relate print offset IP association table

Field name	describe	data type	length	Not empty	remarks
ID	Primary key	VARCHAR	255	TRUE
CHILDIP	Associated client IP	VARCHAR	20	FALSE	Associated table fields fine_print_offset>id
MOTHERID	The ID field corresponding to the print offset table	VARCHAR	255	FALSE

13.4 FINE_REMOTE_DESIGN_Auth remote design user table

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
PATH	Path with remote design permission	VARCHAR	1000	TRUE
PATHTYPE	Path type 0 - file 1 - folder	BOOLEAN	0	TRUE
USERID	User ID	VARCHAR	255	TRUE
USERNAME	user name	VARCHAR	255	TRUE
ROLETYPE	Role type 0: no role 1Department role 2: Custom roles 3: user roles	INTEGER	32	TRUE

13.5 FINE_WRITE_Fill in the temporary storage form by static

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
DATA	Temporary data	VARCHAR	16777216	FALSE
REPORTPATH	Template path	VARCHAR	1000	TRUE
USERNAME	user name	VARCHAR	255	FALSE

13.6 FINE_PROCESS_Extend finereport report report extension table

Field name

describe

data type

length

Not empty

Primary key

VARCHAR

255

TRUE

PROCESSTYPE

Reporting process type

1: report task management

2Reporting process management

3My reporting task

INTEGER

TRUE

13.7 FINE_REPORT_Report extension

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
SHOWTYPE	0 - Fill in 1 - paging 2 - analysis 3 - Form Preview 4 - New report	INTEGER	32	TRUE
TRANSMITPARAMETERS	Custom preview parameters	VARCHAR	65536	FALSE

13.8 FINE_EXCEL_SUBMIT_Task excel batch import permission entity extension table

Note: this table is added for FR project of jar package after December 27, 2018.

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
CREATETIME	Task creation time	TIMESTAMP	26	TRUE
DESCRIPTION	describe	VARCHAR	1000	FALSE
NAME	Task name	VARCHAR	255	TRUE
REPORTPATH	Associated template path	VARCHAR	1000	TRUE
SUBMITTIME	Submission time	TIMESTAMP	26	FALSE

13.9 FINE_VCs template version management table

Field name	describe	data type	length	Not empty
ID	Primary key	VARCHAR	255	TRUE
COMMITCODE	Used to rollback commit	VARCHAR	255	FALSE
COMMITMSG	git commit Msg	VARCHAR	255	FALSE
FILENAME	Template name	VARCHAR	255	FALSE
TIME	Submission time	TIMESTAMP	26	FALSE
USERNAME	user name	VARCHAR	255	FALSE
VERSION	Version number	INTEGER	32	FALSE

前：ビルドインHSQL FineDB紹介

次：PostgreSQL 外部データベース設定

いいね
良くない
閲覧しただけ

中文（简体）中文（繁體） English

日本語