CN119248771A

CN119248771A - Visual database system and computer equipment supporting real-time collaboration

Info

Publication number: CN119248771A
Application number: CN202411211422.3A
Authority: CN
Inventors: 高峰; 王随涛; 张翼
Original assignee: Xi'an Singularity Energy Co ltd
Current assignee: Xi'an Singularity Energy Co ltd
Priority date: 2024-08-30
Filing date: 2024-08-30
Publication date: 2025-01-03

Abstract

The present application discloses a visual database system and computer equipment supporting real-time collaboration, the method comprising: a space management module, used to manage database space, divide the database into multiple spaces, and restrict the use rights of different users to the corresponding space; a user system module, used to manage the user attributes and user rights of users in each space based on the configuration operation of the administrator on the visualization page; 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; an operation audit module, used to query and audit the data modification information of all spaces based on the user rights of different users, and record the data modification information; an API management module, used to access the RESTful interface to query and modify the data in the database management module.

Description

Visual database system supporting real-time collaboration and computer equipment

Technical Field

The application relates to the technical field of databases, in particular to a visual database system supporting real-time collaboration and computer equipment.

Background

Currently, many non-data self-contained enterprises generally face a serious challenge in the process of advancing digital transformation and upgrading, namely, the phenomenon of data islanding widely exists between an internal self-built system and an external purchasing system. These isolated data environments not only hinder the free circulation of information, but also limit the ability of enterprises to fully mine the value of the data. In the process of enterprise building data warehouse and data center, while technical teams can efficiently extract, transform and process business objects, attributes and their values from internal self-building systems and external purchasing systems, those key data elements that are interspersed outside of these systems are often ignored or difficult to integrate effectively. These "missing" data are critical to forming a comprehensive, accurate view of the enterprise data, but are difficult to capture and process due to their unstructured, decentralized storage characteristics.

To make up for this gap, many businesses have to resort to a compromise that relies on manual means to maintain and manage business objects, attributes, and attribute values outside of those systems through Excel off-line tools. These manually consolidated data are then imported into the on-line system for unified data processing and analysis. However, the method can alleviate the problem of data missing to a certain extent, but brings new problems that the consistency of the data is difficult to ensure, and the manually maintained data is easy to be inconsistent due to human error or negligence, so that the accuracy of the data analysis result is affected. The real-time performance is limited, namely, the time delay exists in the data migration process from offline to online, and the requirement of enterprises on real-time data cannot be met. The traceability is insufficient, the version control and change history record functions of the Excel and other tools are limited, and the source and change track of the data are difficult to track effectively. Security risk-storing and transmitting data offline may increase the risk of data leakage, especially in the absence of appropriate security measures.

Thus, for non-data-self-contained enterprises, to truly realize the deepening and upgrading of digital transformation, more efficient, safe and automatic data integration and management solutions must be sought.

Disclosure of Invention

In view of this, the embodiment of the application provides a visual database system and computer equipment supporting real-time collaboration.

According to one aspect of the present application, there is provided a visual database system supporting real-time collaboration, comprising:

The space management module is used for managing the database space, dividing the database into a plurality of spaces, and restricting the use rights of different users under the corresponding spaces;

The user system module is used for managing user attributes and user rights of users in each space based on configuration operation of an administrator on the visual page, wherein the user attributes comprise at least one of organization attributes, personnel attributes and role attributes, and the user rights are initially default rights and can be modified by the administrator;

The system comprises a database management module, a visual page and a display module, wherein the database management module is used for carrying out data storage in each space based on preset database configuration data, and inquiring data stored in the corresponding space based on a data inquiry instruction input by a user on the visual page, wherein the data stored in the database management module accords with the provision of the preset database configuration data, and the preset database configuration data comprises a plurality of data types and specification information corresponding to each data type;

The operation audit module is used for inquiring and auditing the data modification information of all the spaces based on the user rights of different users and recording the data modification information;

And the API management module is used for accessing the RESTful interface and supporting the inquiry and modification of the data in the database management module through the accessed RESTful interface.

In the embodiment of the application, the user system module is also used for setting the first registered user as an administrator, carrying out user registration based on the configuration operation of the administrator, or carrying out user registration based on the registration application after the administrator confirms the registration application, or carrying out user registration based on the acquired registration information of the invited user after the administrator sends out the registration invitation;

The default authority is determined based on the rule that each user has the authority of creating the library and the table under the affiliated space, the library and the table creation user and the administrator have any operation authority to the library and the table, and other users have browsing authority and the authority of modifying the data in the library and the table for the library and the table created by the users except the administrator user and do not have the authority of structurally modifying the library and the table.

In an embodiment of the present application, optionally, the operation audit module is further configured to:

when a user inquires data in each space based on a visual page, acquiring inquiry information, auditing the inquiry information based on user permission to judge whether the inquiry information accords with corresponding user permission, and refusing the inquiry if the inquiry information does not accord with the corresponding user permission;

When a user modifies, adds or deletes data in each space based on a visual page, acquiring data change information, auditing the data change information based on user permission to judge whether the data change information accords with corresponding user permission, if not, recovering data based on pre-change data in the data change information, and recording the data change information and a change result corresponding to the data change information, wherein the data change information comprises change user information, change time and change action information, and the change result is used for indicating whether the change is successful or not;

Wherein querying, modifying, adding or deleting the data under each space comprises querying, modifying, adding or deleting the database structure, the table structure and the data in the table under each space.

In the embodiment of the present application, optionally, the user system module is further configured to allocate different private keys to registered users;

The API management module is further configured to, when receiving a data request transmitted through a RESTful interface, parse the data request, obtain a first key in a request header of the data request, reject the data request if the first key is not an exclusive key of any registered user, and execute the data request if the first key is an exclusive key of any registered user, where the data request includes any one of a data query request, a data addition request, a data deletion request, and a data modification request.

In this embodiment of the present application, optionally, the operation audit module is further configured to audit and process, when a data request through a RESTful interface is received, the data request according to a user permission of a registered user corresponding to a key carried by a request header of the data request.

In the embodiment of the application, the system also comprises a database monitor module;

The database monitor module is used for receiving a message subscription request input based on a visual page, wherein the message subscription request comprises a message subscriber address and subscription data information, monitoring data change in the database management module, judging whether the data change is matched with the subscription data information, if so, notifying the message subscriber of the data change through a preset web hook rule, and the message subscriber comprises a website, other databases or systems.

In this embodiment of the present application, optionally, the API management module is further configured to receive a data synchronization request transmitted through a RESTful interface, analyze a second key and a data synchronization location in a request header of the data synchronization request, reject the data synchronization request if the second key is not an exclusive key of any registered user, determine, based on a user authority of a registered user corresponding to the second key, whether the data synchronization location meets the corresponding user authority, and generate a data synchronization task when the data synchronization task meets the corresponding user authority, where the data synchronization task is configured to synchronize data of an external database to the data synchronization location in the database management module, and the synchronized data includes a database, a table structure, and data in a table, so as to implement data synchronization between the external database and the visual database system;

the database monitor module is further configured to set a monitoring hook based on the data synchronization task, and synchronize the data of the external source database to be synchronized to the synchronization position of the database management module when the monitoring hook is triggered.

In an embodiment of the present application, optionally, the data types include a single line of text, a plurality of lines of text, numbers, currency, percentages, dates, and attachments.

According to a further aspect of the present application, there is provided a computer device deployed with the above-described visualization database system supporting real-time collaboration.

By means of the technical scheme, the visual database system supporting real-time collaboration and the computer equipment provided by the embodiment of the application can flexibly divide the database into a plurality of independent and manageable spaces through the space management module. The space division is not only beneficial to realizing the logic isolation of the data, but also provides exclusive data storage areas for different departments, teams or projects, thereby reducing the formation of data islands. The user architecture module further enhances access control of the data, ensuring that only authorized users can access and manipulate the data in the designated space. This both protects the privacy and security of the data and facilitates data sharing and collaboration across teams. The database management module supports data storage and query based on preset database configuration data, and ensures consistency and standardization of the data. An administrator can easily configure data types and specification information through the visual page without going deep into the underlying database structure, so that convenience and efficiency of data management are improved. The user can quickly acquire the required information by inputting a data query instruction on the visual page without writing complex SQL sentences or relying on a professional database manager. This not only reduces the threshold for data queries, but also increases the efficiency of data utilization. And the operation audit module records and audits the data modification information of all the spaces in real time, so that the transparency and traceability of the data modification are ensured. An administrator can conveniently inquire the history record of any data change, including the modification time, the modification person, the data state before and after modification and the like, and powerful guarantee is provided for the safety and compliance of the data. By combining the authority control function of the user system module, the system can ensure that only users with corresponding authorities can modify the data, thereby further improving the safety of the data. The system supports a real-time collaboration function, so that different users can edit and view data together in the same space, and team collaboration and communication efficiency is improved. At the same time, the system also provides rich visualization tools and data view options, helping users to better understand and analyze the data. The API management module enables the system to be seamlessly integrated with other applications or services by accessing the RESTful interface. The user can realize remote inquiry and modification operation of the data by calling the interfaces, so that the application scene and the functional range of the system are further expanded.

The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIG. 1 is a schematic diagram of a visual database system supporting real-time collaboration according to an embodiment of the present application;

Fig. 2 is a schematic diagram of an operating principle of a visual database system supporting real-time collaboration according to an embodiment of the present application.

Detailed Description

The application will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.

In this embodiment, a visual database system supporting real-time collaboration is provided, as shown in fig. 1, including:

The embodiment of the application provides a visual database system supporting real-time collaboration, which aims to solve the problems of data management, collaboration, security, integration and the like in the process of digitally transforming enterprises by integrating a plurality of core modules. The following is a specific explanation of each module, namely, a space management module, which is responsible for dividing a database into a plurality of logic spaces, wherein each space can be independently managed and is associated with a specific user or user group, so that different departments or projects can have respective data storage spaces, and meanwhile, the safety and isolation of data are ensured. The user system module allows an administrator to configure user attributes (such as organizations, personnel and roles) and user rights on a visual page, and the user rights can be finely set to ensure that each user can only access and operate the authorized data space, so that the fine-granularity rights control improves the security of data and promotes the efficiency of team cooperation. The database management module is responsible for storing and inquiring data, manages the data based on preset database configuration data (comprising data type and specification information), ensures the standardization and consistency of the data, and enables a user to input an inquiry command through a visual page so as to quickly acquire the required data without going deep into the bottom layer of the database. And the operation audit module records and audits the modification operation of all users on the data, and can provide detailed modification records, including modification time, modification personnel and data states before and after modification, so that enterprise tracking data change is facilitated, and traceability and compliance of the data are ensured. And the API management module supports the access of RESTful interfaces and RESTful style interfaces, so that the system can be seamlessly integrated with other application programs or services, and a user or an external system can remotely inquire and modify data in the database through the API, thereby expanding the application scene and the functional range of the system.

By applying the technical scheme of the embodiment, the system can flexibly divide the database into a plurality of independent and manageable spaces through the space management module. The space division is not only beneficial to realizing the logic isolation of the data, but also provides exclusive data storage areas for different departments, teams or projects, thereby reducing the formation of data islands. The user architecture module further enhances access control of the data, ensuring that only authorized users can access and manipulate the data in the designated space. This both protects the privacy and security of the data and facilitates data sharing and collaboration across teams. The database management module supports data storage and query based on preset database configuration data, and ensures consistency and standardization of the data. An administrator can easily configure data types and specification information through the visual page without going deep into the underlying database structure, so that convenience and efficiency of data management are improved. The user can quickly acquire the required information by inputting a data query instruction on the visual page without writing complex SQL sentences or relying on a professional database manager. This not only reduces the threshold for data queries, but also increases the efficiency of data utilization. And the operation audit module records and audits the data modification information of all the spaces in real time, so that the transparency and traceability of the data modification are ensured. An administrator can conveniently inquire the history record of any data change, including the modification time, the modification person, the data state before and after modification and the like, and powerful guarantee is provided for the safety and compliance of the data. By combining the authority control function of the user system module, the system can ensure that only users with corresponding authorities can modify the data, thereby further improving the safety of the data. The system supports a real-time collaboration function, so that different users can edit and view data together in the same space, and team collaboration and communication efficiency is improved. At the same time, the system also provides rich visualization tools and data view options, helping users to better understand and analyze the data. The API management module enables the system to be seamlessly integrated with other applications or services by accessing the RESTful interface. The user can realize remote inquiry and modification operation of the data by calling the interfaces, so that the application scene and the functional range of the system are further expanded.

In the embodiment of the application, the user system module is also used for setting the first registered user as an administrator, carrying out user registration based on configuration operation of the administrator, carrying out user registration based on the registration application after the administrator confirms the registration application, or carrying out user registration based on acquired registration information of the invited user after the administrator sends out registration invitation, wherein default authority is determined based on the rule that each user has authority to create libraries and tables under the affiliated space, the library and table creating user and the administrator have any operation authority to the libraries and tables, and other users have browsing authority and authority to modify data in the libraries and the tables for users except the administrator user, and do not have authority to structurally modify the libraries and the tables.

In this embodiment, for the user hierarchy module, the first registered user is automatically set by the system as an administrator, which enables a quick determination of the management role of the system during the initialization phase, laying the foundation for subsequent user management and system setting. When other users are added, the system allows the administrator to register the users based on the configuration operation of the administrator, and the normalization and the security of the user registration are enhanced. For the user submitting the registration application, the system requires the administrator to complete registration after confirmation, in this way, the administrator can review the identity and qualification of the applicant, and ensure that only the user meeting the requirements can enter the system. The manager can also send out registration invitation, the invited user can register according to the provided registration information, the registration scope of the user is further limited by the way, and the privacy and the security of the system are enhanced. Each user defaults to having the right to create databases and tables under the space to which it belongs, which provides convenience to the user's data management and organization within the designated space. The creation users and administrators of the libraries and tables have arbitrary operation rights to the libraries and tables, including deletion and correction of data, modification of structure, and the like, and this arrangement ensures flexibility and comprehensiveness of management of the data. For libraries and tables created by users other than administrator users, other users default to have browsing rights and rights to modify data, but do not have rights to modify the structure of the libraries and tables, and the arrangement ensures the accessibility of data, avoids random modification of the data structure by unauthorized users, and enhances the security of the data. The method helps enterprises to better manage and utilize the data resources in the digital transformation process.

In the embodiment of the application, optionally, the operation audit module is further used for acquiring query information when a user queries data in each space based on the visual page, auditing the query information based on the user authority to judge whether the query information accords with the corresponding user authority, refusing the query if the query information does not accord with the corresponding user authority, recording the query information and the query result corresponding to the query information, wherein the query information comprises query user information, query time and query action information, the query result is used for indicating whether the query is successful, acquiring data change information when the user modifies, adds or deletes the data in each space based on the visual page, auditing the data change information based on the user authority to judge whether the data change information accords with the corresponding user authority, recovering data based on the data before the change in the data change information if the data change information does not accord with the corresponding user authority, recording the data change information and the change result corresponding to the data change information, wherein the data change information comprises change user information, change time and change action information, and the change action information indicates whether the data is successful or not, and the data is added or deleted in each space, the change table or the structure is added or deleted.

In the embodiment, the operation audit module is not only responsible for monitoring and auditing the data query behavior of the user under each data space, but also responsible for modifying, adding or deleting the audit data and other changing operations, and ensures that all the operations accord with the authority setting of the user, thereby effectively preventing data leakage or illegal tampering. When a user initiates a data query request through a visual page, an operation audit module firstly captures the query information, including query user information (such as a user name, a user ID and the like), query time and specific query action information (such as a query database table, a field, conditions and the like), then, the module can audit the query information in detail according to the authority setting of the user, and confirms whether the user has authority to execute the query operation, if the authority of the user is insufficient to support the query, the operation audit module refuses the query request, so that the data is protected from being accessed by unauthorized users. For all query operations, the operation audit module also records query information and corresponding query results, and the query results are used for indicating whether the query is successfully executed, so that the method has important significance for subsequent scenes such as data audit, problem tracking and the like. In addition, when a user attempts to modify, add or delete data, the operational audit module captures such data change information, including change user information, change time, and specific change action information (e.g., changed data sheets, fields, data values before and after the change, etc.). Similar to the query operation, the module performs authority audit on the data change information to ensure that the user has authority to execute the change operation, and if the authority of the user is not in accordance with the requirement, the module does not execute the change operation, but performs data recovery based on the data before the change in the change information, so as to maintain the original state of the data and prevent illegal tampering. For all data change operations, the operation audit module also records change information and corresponding change results, and the change results are used for indicating whether the change is successfully executed or not, which is important for the scenes such as version control, history tracing and the like of the data. The operation audit module provided by the embodiment of the application provides powerful guarantee for safe access and legal change of data through fine-grained authority audit and comprehensive operation records.

In the embodiment of the application, optionally, the user system module is further configured to allocate different proprietary keys to registered users, and the API management module is further configured to, when receiving a data request transmitted through a RESTful interface, parse the data request, obtain a first key in a request header of the data request, reject the data request if the first key is not a proprietary key of any registered user, and execute the data request if the first key is a proprietary key of any registered user, where the data request includes any one of a data query request, a data new request, a data deletion request, and a data modification request.

In this embodiment, the use of the user architecture module in combination with the API management module further enhances the security of the system and the control capability of data access. The user system module is responsible for distributing a different exclusive key for each registered user, wherein the key is an important identifier of user identity and authority and is used for carrying out identity verification and authority verification in the subsequent data request process, and the system can ensure that only legal users can access and operate data by distributing a unique key for each user. The API management module is an interface layer for providing services to the outside of the system, and is responsible for receiving and processing data requests transmitted through the RESTful interface, where the requests may include various types of data query, data addition, data deletion, data modification, and the like. When the API management module receives a data request, the request is firstly analyzed, a first key in a request header is obtained, the key is identity verification information provided when a user tries to access system resources, the API management module compares the key with the private keys of all registered users stored in the system, if the first key in the request header is not matched with the private keys of any registered user, the request is not verified or illegal in user identity, the API management module refuses the data request, and corresponding error information is returned. If the key matching is successful, indicating that the user identity is legal, 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 the request (such as inquiry, addition, deletion and modification). In this way, the user architecture module and the API management module together construct a secure data access control mechanism. Only registered users with valid private keys can successfully access and operate system data through the RESTful interface, thereby effectively preventing the risk of unauthorized access and data leakage.

In this embodiment, when the operation audit module receives a data request transmitted through the RESTful interface, it performs the steps of first parsing the request header of the data request and extracting the carried key from it. This key is provided by the user at the time of the data request and is used to identify the identity and rights of the user. Then, the operation audit module uses the extracted key to search the corresponding registered user and the user authority thereof in the system. This step is to confirm whether the identity of the user is legal or not, and to acquire the data access and operation rights possessed by the user. After confirming the identity and the authority of the user, the operation auditing module can audit the data request in detail according to the authority setting of the user. The audited content includes the type of request (such as data inquiry, addition, deletion, modification, etc.), the data resource requested to be accessed, whether the operation requested to be executed accords with the authority range of the user, etc. If the data request passes the audit, i.e., the type of request, the accessed data resource, and the performed operation all conform to the user's rights settings, the operation audit module will allow the request to continue to be performed and forwarded to the corresponding service or component for processing. If the request fails the audit, i.e. there is a condition that does not meet the user's rights, the operation audit module will reject the request and return corresponding error information or perform other preset security measures (e.g. log, send alarm, etc.). By the mode, the operation audit module can audit the data operation initiated by the visual page and can also conduct fine-granularity authority control and audit processing on the data request received by the RESTful interface, so that the data access and operation of the whole system are ensured to meet the safety specification and authority requirements.

The embodiment of the application also optionally comprises a database monitor module and a database monitor module, wherein the database monitor module is used for receiving a message subscription request input based on a visual page, the message subscription request comprises a message subscriber address and subscription data information, monitoring data change in the database management module, judging whether the data change is matched with the subscription data information, and if so, notifying the message subscriber of the data change through a preset web hook rule, wherein the message subscriber comprises a website, other databases or a system.

In this embodiment, the system further includes a database listener module to enhance the real-time and flexibility of data change notification. This module focuses on processing the message subscription request based on the visual page input and listens to the data changes in the database management module, so as to inform the subscriber of the data change information in time under specific conditions. First, a message subscription request input by a user through a visualization page is received, wherein the request comprises an address (such as a URL or a callback function address) of a message subscriber and subscribed data information (such as a specific data table, a field or a condition). After the subscription request is received, the database listener module will begin listening for data changes in the database management module, including but not limited to, data additions, deletions, modifications, and the like. For each data change that occurs, the database listener module will match it with all subscribed data information, checking whether the changed data matches the subscriber specified data table, field or condition. If a certain data change matches the subscription condition of the subscriber, the database listener module will send a data change notification to the address provided by the subscriber according to the preset web hook rules (an HTTP callback mechanism). In this way, subscribers can receive data change information of their interest in real time and take corresponding actions accordingly. By monitoring the data change in the database in real time, the subscriber can acquire the latest data state almost without delay, and the subscriber can flexibly define the subscription condition according to own requirements and only receive the data change information concerned by the subscriber, thereby avoiding unnecessary information interference.

In the embodiment of the application, optionally, the API management module is further configured to receive a data synchronization request transmitted through a RESTful interface, analyze a second key and a data synchronization position in a request header of the data synchronization request, reject the data synchronization request if the second key is not an exclusive key of any registered user, determine whether the data synchronization position meets a corresponding user authority based on a user authority of the registered user corresponding to the second key if the second key is an exclusive key of any registered user, and generate a data synchronization task when the data synchronization task meets the corresponding user authority, where the data synchronization task is configured to synchronize the data of the external database to the data synchronization position in the database management module, the synchronized data includes a database, a table structure, and data in a table to realize data synchronization between the external database and the visual database system, and the database monitor module is further configured to set a monitoring hook based on the data synchronization task, and synchronize the data of the external database to be synchronized to the synchronization position of the database management module when the monitoring hook is triggered.

In this embodiment, the API management module receives a data synchronization request transmitted over the RESTful interface, which contains not only the information required for user authentication (e.g., the second key), but also specifies the target location of the data synchronization (i.e., the data synchronization location). The API management module first verifies whether the second key in the request header is the private key of any registered user. If the keys do not match, indicating that the identity of the requester is not verified or illegitimate, the request will be denied. If the keys are matched, further based on the user rights of the registered users corresponding to the keys, whether the data synchronization position specified in the request accords with the rights range of the users is judged. If the data synchronization position meets the authority requirement of the user, the API management module generates a data synchronization task which is used as the basis for the subsequent database monitor module to execute the data synchronization operation. Based on the data synchronization task generated by the API management module, the database listener module will begin listening for synchronized data transmitted over the RESTful interface, which may be from another system, application or data source, that is sent to the present system in a standardized manner over the RESTful interface. Upon receipt of the synchronization data, the database listener module will synchronize it to the database management module at the synchronization location specified by the requestor in the data synchronization request and having passed the verification of the user's rights. By supporting the data synchronization request of the RESTful interface, the system can exchange and synchronize data with other systems or applications more flexibly, the mobility and usability of the data are improved, and by means of a double mechanism of key verification and authority judgment, only legal users can initiate the data synchronization request and only synchronize the data to the positions which the users have access to, so that the safety and the integrity of the data are protected. The user can conveniently initiate a data synchronization request through a visual page or a RESTful interface, and view the synchronization progress and the result in real time, so that the working efficiency and the satisfaction are improved.

By applying the technical scheme of the embodiment, the data interaction effect that the traditional database can be realized only by configuring a data synchronization mechanism and writing a data synchronization interface is solved by means of synchronizing data to the outside and the inside in real time through the B/S architecture page obtained by seeing, the graphical database operation interface which can be directly operated by non-technical personnel is provided, the requirements that all database structure operations and data operations can be queried, recorded and audited are provided, and the traceability requirement of the data is more comprehensively ensured. In the process of enterprise digital transformation and digital upgrading, the method faces the difficulties that data synchronization interfaces are required to be frequently synchronized and written among a plurality of business system data. The data synchronization configuration and actions do not need very specialized software engineers and programmers to write the data synchronization configuration and the data synchronization codes, and after the common business personnel master the data synchronization configuration, the data synchronization requirements can be finished in a manner of just-in-time obtaining. The method has the advantages that the efficiency of data synchronization, configuration and operation is greatly improved, fine data tracing support is provided through an operation and trace mode, data use personnel can easily contact the data, the high customization requirements of data synchronization and service modification are effectively met, and the method has strong innovation and practicability in the development of an actual service system.

In a specific application scenario, as shown in fig. 2, a schematic diagram of the working principle of a visual database system supporting real-time collaboration is shown, where the visual database system includes a plurality of internal and external systems, databases and data processing flows. The following is an explanation of the parts in the drawings:

1. Internal self-built systems 1 to n, which are systems developed internally by the organization, can interact with the real-time collaborative visualization database system through a real-time interface based on the visualization page.

2. The external self-built systems 1 to n are external systems, and can also exchange data with the real-time collaborative visual database through a real-time interface.

3. Real-time collaborative visualization database-a core component provided by embodiments of the present application can receive real-time data from internal and external systems and store the data in multiple databases (database 1 through database n).

4. Databases 1 to n, which are databases for storing real-time data. Each database may store a different type or source of data.

5. Analysis database-this is a database for data analysis that can receive real-time data from multiple databases and possibly aggregate, clean and convert the data for subsequent analysis.

6. Offline data this section represents a non-real time data source such as an Excel file. These data may be imported into the analysis database through a non-real time interface.

7. Real-time and non-real-time interfaces-real-time data flows are represented by solid arrows in the figure and non-real-time data flows are represented by dashed arrows. Real-time data streams are typically used to process scenes that require immediate response, while non-real-time data streams are used to process batches of data or scenes that do not require immediate response.

In particular, the internal and external systems may send data to the real-time collaborative visualization database via the real-time interface based on the visualization page or API interface. These data are stored in real time in multiple databases and possibly synchronized in real time into an analysis database for real time analysis and decision support. Offline data (e.g., excel files) is imported into the analysis database via a non-real-time interface. Such data may be used in scenarios such as historical analysis, report generation, etc. In addition, data interception can be performed based on the database interceptor module to realize data flow and synchronization between the internal and external systems and the databases 1 to n, wherein the contents of the data flow and synchronization comprise database, table and table data. This architecture scheme demonstrates how data from different systems and data sources can be aggregated into one analysis database for data analysis and decision support by way of real-time and non-real-time data integration. The real-time collaborative visualization database plays a key role in data aggregation and distribution, and ensures the real-time performance and usability of the data.

The embodiment of the application also provides a computer device which is provided with the visual database system supporting real-time collaboration, and can be specifically a personal computer, a server, a network device and the like. Wherein the processor of the computer device is configured 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, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing location information. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement the steps in the method embodiments.

It will be appreciated by those skilled in the art that the structure of the computer device described above is merely a partial structure related to the present application and does not constitute a limitation of the computer device to which the present application is applied, and that a specific computer device may include more or fewer components, or may combine certain components, or have different arrangements of components.

In one embodiment, a computer readable storage medium is provided, which may be non-volatile or volatile, and on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

The user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present 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, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. A visual database system supporting real-time collaboration, comprising:

2. The visualization database system supporting real-time collaboration of claim 1,

The user system module is also used for setting a first registered user as an administrator, carrying out user registration based on configuration operation of the administrator, carrying out user registration based on a registration application after the administrator confirms the registration application, or carrying out user registration based on the acquired registration information of the invited user after the administrator sends out registration invitation;

3. The visualization database system supporting real-time collaboration of claim 2, wherein the operation audit module is further configured to:

4. The visual database system supporting real-time collaboration according to claim 1, wherein said user hierarchy module is further configured to assign distinct proprietary keys to registered users;

5. The visual database system supporting real-time collaboration according to claim 4, wherein the operation auditing module is further configured to audit and process the data request according to a user authority of a registered user corresponding to a key carried by a request header of the data request when the data request through the RESTful interface is received.

6. The visualization database system supporting real-time collaboration of claim 4, further comprising a database listener module;

7. The visual database system supporting real-time collaboration according to claim 6, wherein the API management module is further configured to receive a data synchronization request transmitted through a RESTful interface, parse a second key and a data synchronization location in a request header of the data synchronization request, reject the data synchronization request if the second key is not a private key of any registered user, determine, based on a user authority of the registered user corresponding to the second key, whether the data synchronization location meets the corresponding user authority, and generate a data synchronization task when the data synchronization task meets the corresponding user authority, where the data synchronization task is configured to synchronize data of an external database to the data synchronization location in the database management module, and the synchronized data includes a database, a table structure, and data in a table, so as to implement data synchronization between the external database and the visual database system;

8. The visualization database system supporting real-time collaboration of claim 1, wherein the data types include single line text, multiple line text, numbers, currency, percentages, dates, attachments.

9. The visualization database system supporting real-time collaboration according to any one of claims 1 to 8, wherein the visualization database system supporting real-time collaboration is deployed with a development kit jdk, a distributed object storage service minio, a distributed stream processing platform kafka, a data structure storage system rediss, an open source relational database management system mysql so as to run back-end codes based on jdk, store files uploaded in the visualization database supporting real-time collaboration based on minio, decouple network requests from back-end processing capability when high concurrency is completed based on kafka, avoid back-end processing capability overload, store data objects in the visualization database product requiring temporary storage and cache results obtained based on rediss, and persist structured data specific to each library under each table based on mysql.

10. A computer device, characterized in that a visualization database system supporting real-time collaboration according to any of claims 1 to 9 is deployed.