Visual database system supporting real-time collaboration and computer equipment

Abstract

The invention discloses a visual database system supporting real-time collaboration and computer equipment, and the system comprises a space management module which is used for managing a database space and dividing a database into a plurality of spaces, and the use permissions of different users are restrained to be in the corresponding spaces; the user system module is used for managing user attributes and user permissions of the users in each space based on configuration operation of an administrator on the visual page; the database management module is used for performing data storage in each space based on preset database configuration data, and querying the data stored in the corresponding space based on a data query instruction input by a user on the visual page; the operation auditing module is used for querying and auditing the data modification information of all the spaces based on the user permissions of different users and recording the data modification information; and the API management module is used for accessing a RESTful interface to query and modify the data in the database management module.

Description

Technical Field

[0001] The present application relates to the field of database technology, and in particular to a visual database system and computer equipment supporting real-time collaboration. Background Art

[0002] At present, many non-data-owning enterprises are generally facing a severe challenge in the process of promoting digital transformation and upgrading: data silos are widely present between internal self-built systems and external procurement systems. These isolated data environments not only hinder the free flow of information, but also limit the ability of enterprises to fully tap the value of data. In the process of building data warehouses and data centers, although the technical team can efficiently extract, convert and process business objects, attributes and their values ​​from internal self-built systems and external procurement systems, those key data elements scattered outside these systems are often ignored or difficult to effectively integrate. These "lost" data are crucial to forming a comprehensive and accurate view of enterprise data, but they are difficult to capture and process due to their unstructured and decentralized storage characteristics.

[0003] In order to fill this gap, many companies have to adopt a compromise solution: relying on manual means to maintain and manage business objects, attributes and attribute values ​​outside the system through offline tools such as Excel. Subsequently, these manually sorted data are imported into the online system for unified data processing and analysis. However, although this method has alleviated the problem of missing data to a certain extent, it has also brought new problems: Data consistency is difficult to ensure: Manually maintained data is prone to inconsistency due to human errors or negligence, affecting the accuracy of data analysis results. Limited real-time performance: There is a time delay in the data migration process from offline to online, which cannot meet the company's demand for real-time data. Insufficient traceability: The version control and change history functions of tools such as Excel are limited, making it difficult to effectively track the source and change trajectory of data. Security risks: Offline storage and transmission of data may increase the risk of data leakage, especially in the absence of appropriate security measures.

[0004] Therefore, for non-data-owning enterprises, in order to truly deepen and upgrade digital transformation, they must seek more efficient, secure and automated data integration and management solutions. Summary of the invention

[0005] In view of this, an embodiment of the present application provides a visual database system and a computer device that support real-time collaboration.

[0006] According to one aspect of the present application, a visual database system supporting real-time collaboration is provided, characterized in that it includes:

[0007] The space management module is used to manage the database space, divide the database into multiple spaces, and restrict the use rights of different users to the corresponding space;

[0008] A user system module, which is used to manage the user attributes and user rights of users in each space based on the configuration operations of the administrator on the visualization page. The user attributes include at least one of organization attributes, personnel attributes and role attributes. The user rights are initially default rights and can be modified by the administrator;

[0009] A database management module, used to store data in each space based on preset database configuration data, and query the data stored in the corresponding space based on the data query instruction input by the user on the visualization page, wherein the data stored in the database management module conforms to the provisions of the preset database configuration data, and the preset database configuration data includes multiple data types and specification information corresponding to each data type;

[0010] The operation audit module is used to query and audit the data modification information of all spaces based on the user permissions of different users, and record the data modification information;

[0011] The API management module is used to access the RESTful interface and support querying and modifying the data in the database management module through the accessed RESTful interface.

[0012] In the embodiment of the present application, optionally, the user system module is further used to set the first registered user as an administrator; perform user registration based on the configuration operation of the administrator, or perform user registration based on the registration application after the administrator confirms the registration application, or perform user registration based on the registration information of the invited user after the administrator sends a registration invitation;

[0013] The default permissions are determined based on the following rules: Each user has the permission to create libraries and tables in the space to which they belong; the users who create libraries and tables and the administrator have the permission to perform any operations on the libraries and tables; for libraries and tables created by users other than the administrator, other users have the permission to browse and modify the data in the libraries and tables, but do not have the permission to modify the structure of the libraries and tables.

[0014] In the embodiment of the present application, optionally, the operation audit module is further used to:

[0015] When a user queries the data under each space based on the visualization page, query information is obtained, and the query information is audited based on the user authority to determine whether the query information complies with the corresponding user authority. If not, the query is rejected; and the query information and the query result corresponding to the query information are recorded, wherein the query information includes query user information, query time and query action information, and the query result is used to indicate whether the query is successful;

[0016] When a user modifies, adds or deletes data under each space based on a visualization page, data change information is obtained, and the data change information is audited based on user permissions to determine whether the data change information complies with the corresponding user permissions. If not, data recovery is performed based on the pre-change data in the data change information; and the data change information and the change result corresponding to the data change information are recorded, wherein the data change information includes change user information, change time and change action information, and the change result is used to indicate whether the change is successful;

[0017] The querying, modifying, adding or deleting the data in each space includes the querying, modifying, adding or deleting the library structure, table structure and the data in the table in each space.

[0018] In the embodiment of the present application, optionally, the user system module is further used to allocate different exclusive keys to registered users;

[0019] The API management module is also used to parse the data request transmitted through the RESTful interface, obtain the first key in the request header of the data request, and reject the data request if the first key is not the exclusive key of any registered user; if the first key is the exclusive key of any registered user, execute the data request, wherein the data request includes any one of a data query request, a data addition request, a data deletion request, and a data modification request.

[0020] In an embodiment of the present application, optionally, the operation audit module is also used to audit and process the data request according to the user rights of the registered user corresponding to the key carried in the request header of the data request when a data request is received through the RESTful interface.

[0021] In the embodiment of the present application, optionally, it also includes: a database listener module;

[0022] The database listener module is used to receive a message subscription request based on a visualization page input, wherein the message subscription request includes a message subscriber address and subscription data information, monitors data changes in the database management module, and determines whether the data changes match the subscription data information. If they match, the data changes are notified to the message subscriber through a preset web hook rule, and the message subscriber includes a website, other database or system.

[0023] In an embodiment of the present application, optionally, the API management module is further used to receive a data synchronization request transmitted through a RESTful interface, parse the second key and the data synchronization position in the request header of the data synchronization request, and reject the data synchronization request if the second key is not an exclusive key of any registered user; if the second key is an exclusive key of any registered user, then based on the user rights of the registered user corresponding to the second key, determine whether the data synchronization position complies with the corresponding user rights, and generate a data synchronization task if it complies, wherein the data synchronization task is used to synchronize the exogenous database data to the data synchronization position in the database management module, and the synchronized data includes libraries, table structures, and data in tables, so as to realize data synchronization between the exogenous database and the visual database system;

[0024] The database listener module is further used to set a listening hook based on the data synchronization task, and when the listening hook is triggered, the external database data to be synchronized is synchronized to the synchronization position of the database management module.

[0025] In the embodiment of the present application, optionally, the data type includes single-line text, multi-line text, number, currency, percentage, date, and attachment.

[0026] According to another aspect of the present application, a computer device is provided, which is deployed with the above-mentioned visual database system supporting real-time collaboration.

[0027] By means of the above technical solution, a visual database system and computer device supporting real-time collaboration provided by the embodiment of the present application can flexibly divide the database into multiple independent and manageable spaces through the space management module. This space division not only helps to achieve logical isolation of data, but also provides exclusive data storage areas for different departments, teams or projects, thereby reducing the formation of data islands. The user system module further strengthens the access control of data to ensure that only authorized users can access and operate data in the specified space. This not only protects the privacy and security of data, but also promotes data sharing and collaboration across teams. The database management module supports data storage and query based on preset database configuration data, ensuring the consistency and standardization of data. Administrators can easily configure data types and specification information through the visualization page without going deep into the underlying database structure, thereby improving the convenience and efficiency of data management. Users can quickly obtain the required information by entering data query instructions on the visualization page without writing complex SQL statements or relying on professional database administrators. This not only lowers the threshold for data query, but also improves the efficiency of data utilization. The operation audit module records and audits the data modification information of all spaces in real time, ensuring the transparency and traceability of data modification. Administrators can easily query the history of any data changes, including modification time, modifier, and data status before and after modification, etc., which provides strong protection for data security and compliance. Combined with the permission control function of the user system module, the system can ensure that only users with corresponding permissions can modify the data, further improving the security of the data. The system supports real-time collaboration, allowing different users to edit and view data together in the same space, promoting team collaboration and communication efficiency. At the same time, the system also provides a wealth of visualization tools and data view options to help users better understand and analyze data. The API management module enables the system to be seamlessly integrated with other applications or services by accessing the RESTful interface. Users can call these interfaces to implement remote query and modification operations on data, further expanding the application scenarios and functional scope of the system.

[0028] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0030] Figure 1 A schematic diagram of the structure of a visual database system supporting real-time collaboration provided by an embodiment of the present application is shown;

[0031] Figure 2 A schematic diagram showing the working principle of a visual database system supporting real-time collaboration provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0032] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0033] In this embodiment, a visual database system supporting real-time collaboration is provided. Figure 1 As shown, including:

[0034] The space management module is used to manage the database space, divide the database into multiple spaces, and restrict the use rights of different users to the corresponding space;

[0035] A user system module, which is used to manage the user attributes and user rights of users in each space based on the configuration operations of the administrator on the visualization page. The user attributes include at least one of organization attributes, personnel attributes and role attributes. The user rights are initially default rights and can be modified by the administrator;

[0036] A database management module, used to store data in each space based on preset database configuration data, and query the data stored in the corresponding space based on the data query instruction input by the user on the visualization page, wherein the data stored in the database management module conforms to the provisions of the preset database configuration data, and the preset database configuration data includes multiple data types and specification information corresponding to each data type;

[0037] The operation audit module is used to query and audit the data modification information of all spaces based on the user permissions of different users, and record the data modification information;

[0038] The API management module is used to access the RESTful interface and support querying and modifying the data in the database management module through the accessed RESTful interface.

[0039] The embodiment of the present application proposes a visual database system that supports real-time collaboration. The system integrates multiple core modules to solve the problems of data management, collaboration, security and integration encountered in the process of digital transformation of enterprises. The following is a specific explanation of each module: Space management module: This module is responsible for dividing the database into multiple logical spaces. Each space can be managed independently and is associated with a specific user or user group, so that different departments or projects can have their own data storage space, while ensuring the security and isolation of the data. User system module: This module allows administrators to configure user attributes (such as organization, personnel, role) and user permissions on the visualization page. User permissions can be set finely to ensure that each user can only access and operate the data space for which they are authorized. This fine-grained permission control improves data security and promotes the efficiency of team collaboration. Database management module: This module is responsible for the storage and query of data. It manages data based on preset database configuration data (including data types and specification information) to ensure the standardization and consistency of data. Users can enter query instructions through the visualization page to quickly obtain the required data without going deep into the bottom layer of the database. Operation audit module: This module records and audits all users' modification operations on data. No matter which user makes what modification in which space, the operation audit module can provide detailed modification records, including modification time, modifier, and data status before and after modification, which helps enterprises track data changes and ensure data traceability and compliance. API management module: This module supports access to RESTful interfaces and RESTful-style interfaces, allowing the system to be seamlessly integrated with other applications or services. Through APIs, users or external systems can remotely query and modify data in the database, thereby expanding the application scenarios and functional scope of the system.

[0040] By applying the technical solution of this embodiment, through the space management module, the system can flexibly divide the database into multiple independent and manageable spaces. This space division not only helps to achieve logical isolation of data, but also provides exclusive data storage areas for different departments, teams or projects, thereby reducing the formation of data islands. The user system module further strengthens the access control of data to ensure that only authorized users can access and operate data in the specified space. This not only protects the privacy and security of data, but also promotes data sharing and collaboration across teams. The database management module supports data storage and query based on preset database configuration data, ensuring the consistency and standardization of data. Administrators can easily configure data types and specification information through the visualization page without going deep into the underlying database structure, thereby improving the convenience and efficiency of data management. Users can quickly obtain the required information by entering data query instructions on the visualization page without writing complex SQL statements or relying on professional database administrators. This not only lowers the threshold for data query, but also improves the efficiency of data utilization. The operation audit module records and audits the data modification information of all spaces in real time, ensuring the transparency and traceability of data modification. Administrators can easily query the history of any data changes, including modification time, modifier, and data status before and after modification, etc., which provides strong protection for data security and compliance. Combined with the permission control function of the user system module, the system can ensure that only users with corresponding permissions can modify the data, further improving the security of the data. The system supports real-time collaboration, allowing different users to edit and view data together in the same space, promoting team collaboration and communication efficiency. At the same time, the system also provides a wealth of visualization tools and data view options to help users better understand and analyze data. The API management module enables the system to be seamlessly integrated with other applications or services by accessing the RESTful interface. Users can call these interfaces to implement remote query and modification operations on data, further expanding the application scenarios and functional scope of the system.

[0041] In an embodiment of the present application, optionally, the user system module is also used to set the first registered user as an administrator; perform user registration based on the configuration operation of the administrator, or perform user registration based on the registration application after the administrator confirms the registration application, or perform user registration based on the registration information of the invited user after the administrator sends a registration invitation; wherein, the default permissions are determined based on the following rules: each user has the permission to create libraries and tables under the space to which they belong; the user who creates the library and table and the administrator have any operation permission on the library and table; for libraries and tables created by users other than the administrator user, other users have browsing permissions and permissions to modify the data in the libraries and tables, but do not have permissions to modify the structure of the libraries and tables.

[0042] In this embodiment, for the user system module, the first registered user is automatically set as an administrator by the system, which enables the system's management role to be quickly determined in the initialization phase, laying the foundation for subsequent user management and system settings. When adding other users, the system allows the administrator to register users based on their own configuration operations, which enhances the standardization and security of user registration. For users who submit registration applications, the system requires the administrator to confirm before completing the registration. In this way, the administrator can review the identity and qualifications of the applicant to ensure that only users who meet the requirements can enter the system. The administrator can also issue a registration invitation, and the invited users can register according to the provided registration information. This method further limits the user's registration scope and enhances the privacy and security of the system. Each user has the authority to create databases and tables in the space to which they belong by default, which provides convenience for users to manage and organize data in the specified space. The users who create the library and table and the administrator have any operation authority over the library and table, including the addition, deletion, modification and query of data and the modification of the structure, etc. This setting ensures the flexibility of the data and the comprehensiveness of management. For libraries and tables created by users other than administrators, other users have the permission to browse and modify data by default, but do not have the permission to modify the structure of libraries and tables. This setting not only ensures the accessibility of data, but also prevents unauthorized users from arbitrarily changing the data structure, thus enhancing data security. This helps enterprises better manage and utilize data resources during the digital transformation process.

[0043] In an embodiment of the present application, optionally, the operation audit module is also used to: when a user queries the data under each space based on a visualization page, obtain query information, audit the query information based on user permissions to determine whether the query information complies with the corresponding user permissions, and if not, reject the query; and record the query information and the query result corresponding to the query information, wherein the query information includes query user information, query time and query action information, and the query result is used to indicate whether the query is successful; when a user modifies, adds or deletes the data under each space based on a visualization page, obtain data change information, and audit the data change information based on user permissions to determine whether the data change information complies with the corresponding user permissions, and if not, restore the data based on the pre-change data in the data change information; and record the data change information and the change result corresponding to the data change information, wherein the data change information includes change user information, change time and change action information, and the change result is used to indicate whether the change is successful; wherein querying, modifying, adding or deleting the data under each space includes querying, modifying, adding or deleting the library structure, table structure, and data in the table under each space.

[0044] In this embodiment, the operation audit module is not only responsible for monitoring and auditing the user's data query behavior under each data space, but also responsible for auditing data modification, addition or deletion and other change operations, ensuring that all operations comply with the user's permission settings, thereby effectively preventing data leakage or illegal tampering. When a user initiates a data query request through a visualization page, the operation audit module first captures these query information, including query user information (such as user name, user ID, etc.), query time, and specific query action information (such as the queried database table, field, condition, etc.); then, the module will perform a detailed audit of the query information according to the user's permission settings to confirm whether the user has the right to perform the query operation. If the user's authority is not sufficient to support the query, the operation audit module will reject this query request, thereby protecting the data from being accessed by unauthorized users. For all query operations, the operation audit module will also record the query information and its corresponding query results. The query results are used to indicate whether the query is successfully executed, which is of great significance for subsequent data audits, problem tracking and other scenarios. In addition, when the user tries to modify, add or delete data, the operation audit module will capture these data change information, including change user information, change time and specific change action information (such as the changed data table, field, data values ​​before and after the change, etc.). Similar to the query operation, the module will perform permission audit on the data change information to ensure that the user has the authority to perform the change operation. If the user's authority does not meet the requirements, the module will not perform the change operation, but will perform data recovery based on the pre-change data in the change information to maintain the original state of the data and prevent illegal tampering. For all data change operations, the operation audit module will also record the change information and its corresponding change results. The change results are used to indicate whether the change is successfully executed, which is crucial for scenes such as version control and historical tracing of data. The operation audit module of the embodiment of the present application provides a strong guarantee for secure access to data and legal changes through fine-grained permission auditing and comprehensive operation records.

[0045] In an embodiment of the present application, optionally, the user system module is also used to assign different exclusive keys to registered users; the API management module is also used to parse the data request when receiving a data request transmitted through a RESTful interface, and obtain the first key in the request header of the data request. If the first key is not the exclusive key of any registered user, the data request is rejected; if the first key is the exclusive key of any registered user, the data request is executed, wherein the data request includes any one of a data query request, a data addition request, a data deletion request, and a data modification request.

[0046] In this embodiment, the combined use of the user system module and the API management module further enhances the security of the system and the control ability of data access. The user system module is responsible for assigning a different exclusive key to each registered user. This key is an important identifier of the user's identity and authority, and is used for identity authentication and authority verification in the subsequent data request process. By assigning a unique key to each user, the system can ensure that only legitimate users can access and operate data. The API management module is the interface layer for the system to provide services to the outside world. It is responsible for receiving and processing data requests transmitted through the RESTful interface. These requests may include data query, data addition, data deletion, data modification and other types. When the API management module receives a data request, it will first parse the request and obtain the first key in the request header. This key is the authentication information provided by the user when trying to access system resources. The API management module will compare this key with the exclusive keys of all registered users stored in the system. If the first key in the request header does not match the exclusive key of any registered user, it means that the identity of the user initiating the request is not verified or illegal. The API management module will reject the data request and return the corresponding error message. If the key matches successfully, it means that the user identity is legitimate, and the API management module will continue to execute the data request and call the corresponding service or resource for processing according to the type of request (such as query, add, delete, modify). In this way, the user system module and the API management module jointly build a secure data access control mechanism. Only registered users with valid exclusive keys can successfully access and operate system data through the RESTful interface, thereby effectively preventing the risk of unauthorized access and data leakage.

[0047] In an embodiment of the present application, optionally, the operation audit module is also used to audit and process the data request according to the user rights of the registered user corresponding to the key carried in the request header of the data request when a data request is received through the RESTful interface.

[0048] In this embodiment, when the operation audit module receives a data request transmitted through a RESTful interface, it will perform the following steps: First, the operation audit module will parse the request header of the data request and extract the carried key from it. This key is provided by the user when making a data request and is used to identify the user's identity and authority. Next, the operation audit module will use the extracted key to find the corresponding registered user and its user authority in the system. This step is to confirm whether the user's identity is legal and obtain the data access and operation permissions owned by the user. After confirming the user's identity and permissions, the operation audit module will perform a detailed audit of the data request according to the user's permission settings. The audit content includes the type of request (such as data query, addition, deletion, modification, etc.), the data resources requested to be accessed, and whether the operation requested to be performed complies with the user's authority range. If the data request passes the audit, that is, the type of request, the data resources accessed, and the operation performed all comply with the user's permission settings, then the operation audit module will allow the request to continue to execute and forward it to the corresponding service or component for processing. If the request fails the audit, that is, it does not meet the user's permissions, the operation audit module will reject the request and return the corresponding error message or execute other preset security measures (such as logging, sending alarms, etc.). In this way, the operation audit module can not only audit the data operations initiated through the visualization page, but also perform fine-grained permission control and audit processing on the data requests received through the RESTful interface, thereby ensuring that the data access and operations of the entire system comply with security specifications and permission requirements.

[0049] In an embodiment of the present application, optionally, it also includes: a database listener module; a database listener module, used to receive a message subscription request based on a visualization page input, the message subscription request includes a message subscriber address and subscription data information, monitors data changes in the database management module, and determines whether the data changes match the subscription data information. If they match, the data changes are notified to the message subscribers through preset web hook rules, and the message subscribers include websites, other databases or systems.

[0050] In this embodiment, the system also includes a database listener module to enhance the real-time and flexibility of data change notification. This module focuses on processing message subscription requests based on visual page input, and monitors data changes in the database management module, so as to timely notify subscribers of data change information under specific conditions. First, receive message subscription requests from users input through the visual page, which contain the address of the message subscriber (such as URL or callback function address) and the subscribed data information (such as specific data tables, fields or conditions). After the subscription request is received, the database listener module will start to monitor the data changes in the database management module, including but not limited to operations such as adding, deleting, and modifying data. For each data change that occurs, the database listener module will match it with all subscribed data information to check whether the changed data meets the data table, field or condition specified by the subscriber. If a data change matches the subscriber's subscription condition, the database listener module will send the data change notification to the address provided by the subscriber according to the preset web hook rule (an HTTP callback mechanism). In this way, subscribers can receive the data change information they care about in real time and take corresponding actions accordingly. By monitoring data changes in the database in real time, subscribers can obtain the latest data status with almost no delay. Subscribers can flexibly define subscription conditions according to their needs and only receive data change information they care about, thus avoiding unnecessary information interference.

[0051] In an embodiment of the present application, optionally, the API management module is also used to receive a data synchronization request transmitted through a RESTful interface, parse the second key and data synchronization position in the request header of the data synchronization request, and if the second key is not a dedicated key of any registered user, reject the data synchronization request; if the second key is a dedicated key of any registered user, then based on the user rights of the registered user corresponding to the second key, determine whether the data synchronization position complies with the corresponding user rights, and generate a data synchronization task if it complies, wherein the data synchronization task is used to synchronize the exogenous database data to the data synchronization position in the database management module, and the synchronized data includes libraries, table structures, and data in tables, so as to realize data synchronization between the exogenous database and the visual database system; the database listener module is also used to set a listening hook based on the data synchronization task, and when the listening hook is triggered, the exogenous database data to be synchronized is synchronized to the synchronization position of the database management module.

[0052] In this embodiment, the API management module receives a data synchronization request transmitted through a RESTful interface, which not only contains the information required for user identity authentication (such as the second key), but also specifies the target location of data synchronization (i.e., the data synchronization location). The API management module will first verify whether the second key in the request header is a dedicated key for any registered user. If the keys do not match, it means that the identity of the requester is not verified or illegal, and the request will be rejected. If the keys match, it is further determined based on the user rights of the registered user corresponding to the key whether the data synchronization location specified in the request meets the user's authority range. If the data synchronization location meets the user's authority requirements, the API management module will generate a data synchronization task, which will serve as the basis for the subsequent database listener module to perform data synchronization operations. Based on the data synchronization task generated by the API management module, the database listener module will start to listen to the synchronization data transmitted through the RESTful interface. These data may come from another system, application or data source, and are sent to the present system in a standardized manner through the RESTful interface. Once the synchronization data is received, the database listener module will synchronize it to the synchronization location of the database management module, which is specified by the requester in the data synchronization request and has passed the user authority verification. By supporting data synchronization requests through RESTful interfaces, the system can exchange and synchronize data with other systems or applications more flexibly, improving the liquidity and availability of data. Through the dual mechanisms of key verification and permission judgment, it ensures that only legitimate users can initiate data synchronization requests and can only synchronize data to locations they have access to, thereby protecting the security and integrity of the data. Users can easily initiate data synchronization requests through visual pages or RESTful interfaces, and view synchronization progress and results in real time, improving work efficiency and satisfaction.

[0053] In the embodiment of the present application, optionally, the data type includes single-line text, multi-line text, number, currency, percentage, date, and attachment.

[0054] By applying the technical solution of this embodiment, through the WYSIWYG B / S architecture page, by synchronizing data to the outside and the outside to the inside in real time, the data interaction effect that the traditional database needs to configure the data synchronization mechanism and write the data synchronization interface to achieve in the past is solved, and a graphical database operation interface that non-technical personnel can directly operate is provided, and all database structure operations and data operations can be queried, recorded, and audited. The demand for data traceability is more comprehensively guaranteed. In the process of digital transformation and digital upgrading of enterprises, it is faced with the difficulties of frequent synchronization of data and frequent writing of data synchronization interfaces between multiple business system data. Data synchronization configuration and action no longer require very professional software engineers and programmers to write data synchronization configuration and data synchronization code. After ordinary business personnel master the data synchronization configuration, they can complete the data synchronization requirements in a WYSIWYG manner. The efficiency of data synchronization, configuration, and operation is greatly improved, and fine data traceability support is provided in the form of "operation and traces", which can make data users more easily contact data, and efficiently deliver data synchronization and modify the highly customized requirements of business. This method has strong innovation and practicality in the development of actual business systems.

[0055] In a specific application scenario, such as Figure 2 The figure shows the working principle of a visual database system that supports real-time collaboration, which includes multiple internal and external systems, databases, and data processing processes. The following is an explanation of each part of the figure:

[0056] 1. Internally built systems 1 to internally built systems n: These are systems developed within the organization that can interact with real-time collaborative visual database systems through real-time interfaces based on visual pages.

[0057] 2. External self-built system 1 to external self-built system n: These are external systems that can also exchange data with the real-time collaborative visualization database through a real-time interface.

[0058] 3. Real-time collaborative visual database: A core component provided in an embodiment of the present application, which can receive real-time data from internal and external systems and store the data in multiple databases (database 1 to database n).

[0059] 4. Database 1 to Database n: These are databases used to store real-time data. Each database may store data of different types or sources.

[0060] 5. Analytical database: This is a database used for data analysis. It can receive real-time data from multiple databases and may aggregate, clean and transform the data for subsequent analysis.

[0061] 6. Offline data: This part represents non-real-time data sources, such as Excel files. These data can be imported into the analysis database through a non-real-time interface.

[0062] 7. Real-time and non-real-time interfaces: In the figure, real-time data flows are represented by solid arrows, and non-real-time data flows are represented by dotted arrows. Real-time data flows are usually used to process scenarios that require immediate response, while non-real-time data flows are used to process batch data or scenarios that do not require immediate response.

[0063] Specifically, internal and external systems can send data to a real-time collaborative visual database based on a visualization page or API interface through a real-time interface. These data are stored in multiple databases in real time and may be synchronized to the analysis database in real time for real-time analysis and decision support. Offline data (such as Excel files) are imported into the analysis database through a non-real-time interface. These data may be used in scenarios such as historical analysis and report generation. In addition, data monitoring can also be performed based on the database listener module to achieve data flow and synchronization between internal and external systems and databases 1 to n. The content of data flow and synchronization includes libraries, tables, and table data. This architecture solution shows how to integrate data from different systems and data sources into an analysis database through real-time and non-real-time data integration methods to facilitate data analysis and decision support. The real-time collaborative visual database plays a key role in data aggregation and distribution here, ensuring the real-time and availability of data.

[0064] The embodiment of the present application also provides a computer device, which is deployed with the above-mentioned visual database system supporting real-time collaboration, which can be specifically a personal computer, a server, a network device, etc. The computer device includes a bus, a processor, a memory and a communication interface, and can also include an input and output interface and a display device. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store location information. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps in each method embodiment are implemented.

[0065] Those skilled in the art will appreciate that the structure of the above-mentioned computer device is only a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components, or combine certain components, or have a different arrangement of components.

[0066] In one embodiment, a computer-readable storage medium is provided. The computer-readable storage medium may be non-volatile or volatile, and stores a computer program thereon. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0067] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0068] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0069] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0070] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0071] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A visual database system supporting real-time collaboration, characterized in that: include: The space management module is used to manage the database space, divide the database into multiple spaces, and restrict the use rights of different users to the corresponding space; A user system module, which is used to manage the user attributes and user rights of users in each space based on the configuration operations of the administrator on the visualization page. The user attributes include at least one of organization attributes, personnel attributes and role attributes. The user rights are initially default rights and can be modified by the administrator; A database management module, used to store data in each space based on preset database configuration data, and query the data stored in the corresponding space based on the data query instruction input by the user on the visualization page, wherein the data stored in the database management module conforms to the provisions of the preset database configuration data, and the preset database configuration data includes multiple data types and specification information corresponding to each data type; The operation audit module is used to query and audit the data modification information of all spaces based on the user permissions of different users, and record the data modification information; The API management module is used to access the RESTful interface and support querying and modifying the data in the database management module through the accessed RESTful interface.

2. The visual database system supporting real-time collaboration according to claim 1, characterized in that: The user system module is further used to set the first registered user as an administrator; perform user registration based on the configuration operation of the administrator, or perform user registration based on the registration application after the administrator confirms the registration application, or perform user registration based on the registration information of the invited user after the administrator sends a registration invitation; The default permissions are determined based on the following rules: Each user has the permission to create libraries and tables in the space to which they belong; the users who create libraries and tables and the administrator have the permission to perform any operations on the libraries and tables; for libraries and tables created by users other than the administrator, other users have the permission to browse and modify the data in the libraries and tables, but do not have the permission to modify the structure of the libraries and tables.

3. The visual database system supporting real-time collaboration according to claim 2, characterized in that: The operation audit module is also used for: When a user queries the data under each space based on the visualization page, query information is obtained, and the query information is audited based on the user authority to determine whether the query information complies with the corresponding user authority. If not, the query is rejected; and the query information and the query result corresponding to the query information are recorded, wherein the query information includes query user information, query time and query action information, and the query result is used to indicate whether the query is successful; When a user modifies, adds or deletes data under each space based on a visualization page, data change information is obtained, and the data change information is audited based on user permissions to determine whether the data change information complies with the corresponding user permissions. If not, data recovery is performed based on the pre-change data in the data change information; and the data change information and the change result corresponding to the data change information are recorded, wherein the data change information includes change user information, change time and change action information, and the change result is used to indicate whether the change is successful; The querying, modifying, adding or deleting the data in each space includes the querying, modifying, adding or deleting the library structure, table structure and the data in the table in each space.

4. The visual database system supporting real-time collaboration according to claim 1, characterized in that: The user system module is also used to allocate different exclusive keys to registered users; The API management module is also used to parse the data request transmitted through the RESTful interface, obtain the first key in the request header of the data request, and reject the data request if the first key is not the exclusive key of any registered user; if the first key is the exclusive key of any registered user, execute the data request, wherein the data request includes any one of a data query request, a data addition request, a data deletion request, and a data modification request.

5. The visual database system supporting real-time collaboration according to claim 4, characterized in that: The operation audit module is also used to audit and process the data request when receiving the data request through the RESTful interface according to the user rights of the registered user corresponding to the key carried in the request header of the data request.

6. The visual database system supporting real-time collaboration according to claim 4, characterized in that: Also includes: Database listener module; The database listener module is used to receive a message subscription request based on a visualization page input, wherein the message subscription request includes a message subscriber address and subscription data information, monitors data changes in the database management module, and determines whether the data changes match the subscription data information. If they match, the data changes are notified to the message subscriber through a preset web hook rule, and the message subscriber includes a website, other database or system.

7. The visual database system supporting real-time collaboration according to claim 6, characterized in that: The API management module is further used to receive a data synchronization request transmitted through a RESTful interface, parse the second key and data synchronization position in the request header of the data synchronization request, and reject the data synchronization request if the second key is not a dedicated key for any registered user; if the second key is a dedicated key for any registered user, determine whether the data synchronization position complies with the corresponding user authority based on the user authority of the registered user corresponding to the second key, and generate a data synchronization task if it complies, wherein the data synchronization task is used to synchronize the exogenous database data to the data synchronization position in the database management module, and the synchronized data includes the library, table structure, and data in the table, so as to realize data synchronization between the exogenous database and the visual database system; The database listener module is further used to set a listening hook based on the data synchronization task, and when the listening hook is triggered, the external database data to be synchronized is synchronized to the synchronization position of the database management module.

8. The visual database system supporting real-time collaboration according to claim 1, characterized in that: The data types include single-line text, multi-line text, numbers, currencies, percentages, dates, and attachments.

9. The visual database system supporting real-time collaboration according to any one of claims 1 to 8, characterized in that: The visual database system supporting real-time collaboration is deployed with a development toolkit JDK, a distributed object storage service Minio, a distributed stream processing platform Kafka, a data structure storage system Redis, and an open source relational database management system MySQL, so as to run the backend code based on JDK, store the uploaded files in the real-time collaborative visual database based on Minio, decouple the network request from the backend processing capability when completing high concurrency based on Kafka to avoid overloading the backend processing capability, store the data objects that need to be temporarily stored and obtain cache results at high speed in the real-time collaborative visual database product based on Redis, and persistently store the structured data under each specific library and each table based on MySQL.

10. A computer device, characterized in that: A visual database system supporting real-time collaboration as claimed in any one of claims 1 to 9 is deployed.

Images