Database management system and method

Abstract

The present invention discloses a database management system and method, which belongs to the field of database technology, and the technical problem to be solved is how to efficiently manage multi-source data. It includes a data source driver management module, a data source template extension module and a console tool module; the data source driver management module is used to maintain the integrated data source driver plug-in; the data source template extension module is used to provide different data source management template plug-ins for the console tool module; the console tool module includes a user interface, a scheduling center and a registration center, which interacts with the outside through the user interface, supports users to configure and manage data sources, and supports users to add, delete and modify data sources, handles the monitoring of user operation events through the scheduling center, manages and schedules the data source driver management module and the data source template extension module, and provides registration and implementation of data source driver plug-ins and data source management template plug-ins through the registration center.

Description

Technical Field

[0001] The present invention relates to the field of database technology, in particular to a database management system and method. Background Art

[0002] With the rapid development of information technology and the advancement of enterprise digital transformation, various types of data sources continue to emerge, including traditional relational databases (such as MySQL, PostgreSQL, Oracle, etc.) and non-relational databases that emerged in the big data era (such as MongoDB, Cassandra, HBase, etc.). At the same time, the amount of data inside and outside the enterprise is also growing rapidly. These data types are diverse and in different formats. How to efficiently manage and utilize these multi-source data has become a major challenge facing enterprises. In an environment where multiple business systems coexist, different systems may use different databases, resulting in data being scattered in different databases. In order to achieve unified management and comprehensive utilization of data, a database management system solution that can integrate multiple database management requirements, has flexible configuration and high compatibility is needed.

[0003] How to efficiently manage multi-source data is a technical problem that needs to be solved. Summary of the invention

[0004] The technical task of the present invention is to provide a database management system and method to solve the technical problem of how to efficiently manage multi-source data in view of the above shortcomings.

[0005] In a first aspect, the present invention provides a database management system, including a data source driver management module, a data source template extension module, and a console tool module;

[0006] The data source driver management module is used to maintain the integrated data source driver plug-in;

[0007] The data source template extension module is used to provide different data source management template plug-ins for the console tool module;

[0008] The console tool module includes a user interface, a scheduling center and a registration center. It interacts with the outside world through the user interface, supports users to configure and manage data sources, and supports users to add, delete and modify data sources. The scheduling center handles the monitoring of user operation events, manages and schedules data source driver management modules and data source template extension modules, and provides registration and implementation of data source driver plug-ins and data source management template plug-ins through the registration center.

[0009] Preferably, the data source driver management module supports developers to upload and update data source driver plug-ins and persist data source driver plug-ins in a database, and supports ordinary users to download data source driver plug-ins.

[0010] Preferably, the data source extension plug-in includes a processor, a configurator and a manager;

[0011] The manager is used to abstract the add, delete, and modify operations of various instance objects of the data source into corresponding action methods, and encapsulate the statements for operating various instance objects of the data source within the action methods;

[0012] The configurator is used to provide the graphical interface and interface instantiation scheduling logic required for the manager operation. The configurator defines the Dialog interface, Page interface, Wizard interface and Configure interface. As a developer, the user implements the dialog box Dialog, page Page and wizard Wizard required for each operation according to the specific business, and implements the Configure interface to instantiate the dialog box Dialog, page Page or wizard Wizard;

[0013] The processor is used to implement the scheduling logic of the configurator and manager, and encapsulate the return results of the manager's action method into commands for processing by the console tool module.

[0014] Preferably, the registration center defines a Driver interface, a DriverFactory interface, a Driver interface, a Plugin interface, and a PluginFactory interface, wherein the Driver interface and the DriverFactory interface are implemented by a data source driver plug-in, and the Plugin interface and the PluginFactory interface are implemented by a data source template extension plug-in;

[0015] Among them, the DriverFactory and PluginFactory implementation classes need to be registered in the DriverRegistry and PluginRegistry of the console tool module main program through plug-in technology. The variable driverFactories of DriverRegistry is used to store the data source driver plug-in implementation class. The stored key value is the value obtained by the getHeader method of the data source driver plug-in implementation class.

[0016] The variable pluginFactories of PluginRegistry is used to store the data source template extension plug-in implementation class. The stored key value is the value obtained by the getHeader method of the data source template extension plug-in implementation class.

[0017] When the user starts the console tool module to add a data source, DriverRegistry finds the matching DriverFactory implementation class through the specified protocol header, calls the createDriver method of DriverFactory, creates a driver instance Driver that connects to the database, and calls the createConnection method of Driver to create a database connection instance.

[0018] Preferably, the dispatch center includes an executor, a listener and a processor;

[0019] The user interface provides a management console and a data query interface, which are used to encapsulate user operations into events and send them to the dispatch center. After the listener listens to the corresponding event, it calls the page defined in the configurator of the data source template extension plug-in through the processor to display it back to the user. According to the user input, the processor calls the manager in the data source template extension plug-in to obtain the corresponding statement processing command, and submits the statement processing command to the executor. The processor parses the statements for operating various instance objects of the data source from the processing command and submits them to the executor. The executor sends the statement to the corresponding data source through the connection instance of the created managed database to complete this operation.

[0020] In a second aspect, the present invention provides a database management method, which manages a database through a database management system as described in any one of the first aspects.

[0021] As a preference, the method comprises the following steps:

[0022] Download compatible data source driver plug-ins and corresponding data source template extension plug-ins;

[0023] Register the data source driver plug-in and data source template extension plug-in in the console tool module;

[0024] Load the registered data source driver plug-in and data source template extension plug-in when the console tool is started to achieve data source integration and management;

[0025] Configure and manage data sources through user interaction with the user interface;

[0026] According to user input, data source instance addition, deletion, modification and query operations are performed through the configured data source driver plug-in and data source template extension plug-in.

[0027] Preferably, according to user input, the operations of adding, deleting, modifying and checking the data source instance are performed through the configured data source driver plug-in and data source template extension plug-in, including the following steps:

[0028] Process user actions as events within the console tool module;

[0029] Call the appropriate plugin configurator and manager to generate command statements for add, delete, modify and query operations;

[0030] Sends command statements through an established connection to the connected data source to perform operations.

[0031] The database management system and method of the present invention have the following advantages: by specifying a database management system with lightweight characteristics, capable of meeting the graphical management requirements of multi-source databases, and having flexible configuration and high compatibility characteristics, the cumbersome steps of managing and operating multi-source databases in a hybrid database environment are avoided, and the operation and maintenance costs are reduced. The plug-in implementation scheme allows users to select and configure suitable plug-ins according to actual needs, thereby customizing the database management system to adapt to different business environments and demand changes, thereby improving the flexibility and scalability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] The present invention is further described below in conjunction with the accompanying drawings.

[0034] Figure 1 This is a structural block diagram of a database management system in Example 1;

[0035] Figure 2 This is a schematic diagram of data flow in a data source driver management module of a database management system in Example 1;

[0036] Figure 3 This is a structural block diagram of a data source template extension management module in a database management system in Example 1;

[0037] Figure 4 See the block diagram for the structure of a console tool module in a database management system in Example 1. DETAILED DESCRIPTION

[0038] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments so that those skilled in the art can better understand the present invention and implement it. However, the embodiments are not intended to limit the present invention. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments may be combined with each other.

[0039] The embodiments of the present invention provide a database management system and method for solving the technical problem of how to efficiently manage multi-source data.

[0040] Embodiment 1:

[0041] The invention discloses a database management system, which comprises a data source drive management module, a data source template expansion module and a console tool module.

[0042] The data source driver management module is used to maintain the integrated data source driver plug-in.

[0043] In this embodiment, the main function of the data source driver management module is to maintain the integrated data source driver; developers can develop a unified interface for the development access console tool module to provide customized driver plug-in development for multi-platform databases to meet the needs of different application scenarios, complete the driver plug-in development, and provide it for ordinary users and other development or operation and maintenance personnel. Figure 2 As shown, the data source driver management module supports developers to upload and update data source driver plug-ins, persist data source driver plug-ins in the database, and supports ordinary users to download data source driver plug-ins.

[0044] The data source template extension module is used to provide different data source management template plug-ins for the console tool module.

[0045] In this embodiment, the main function of the data source plug-in extension module is to provide different data source management template plug-ins for the console tool to support management operations of different data sources.

[0046] Developers maintain data source template extension plug-ins developed for different platforms, which include processors, configurators, and managers.

[0047] The manager is used to abstract the add, delete, and modify operations of various instance objects of the data source into corresponding action methods, and encapsulate statements for operating various instance objects of the data source within the action methods.

[0048] The configurator is used to provide the graphical interface and interface instantiation scheduling logic required for manager operations. The configurator defines the Dialog interface, Page interface, Wizard interface and Configure interface. Users as developers implement the dialog boxes Dialog, Page and Wizard required for each operation according to the specific business, and implement the Configure interface to instantiate the dialog box Dialog, page Page or wizard Wizard.

[0049] The processor is used to implement the scheduling logic of the configurator and manager, and encapsulate the return results of the manager's action method into commands for processing by the console tool module.

[0050] Developers develop template extension plug-ins by developing a unified interface for access console tool module templates for use by ordinary users and other development or operation and maintenance personnel.

[0051] The console tool module includes a user interface, a scheduling center and a registration center. It interacts with the outside world through the user interface, supports users to configure and manage data sources, and supports users to add, delete and modify data sources. The scheduling center handles the monitoring of user operation events, manages and schedules the data source driver management module and the data source template extension module, and provides registration and implementation of data source driver plug-ins and data source management template plug-ins through the registration center.

[0052] In this embodiment, the registration center defines a Driver interface, a DriverFactory interface, a Driver interface, a Plugin interface, and a PluginFactory interface. The Driver interface and the DriverFactory interface are implemented by a data source driver plug-in, and the Plugin interface and the PluginFactory interface are implemented by a data source template extension plug-in.

[0053] Among them, DriverFactory and PluginFactory implementation classes need to be registered in DriverRegistry and PluginRegistry of the main program of the console tool module through plug-in technology. The variable driverFactories of DriverRegistry is used to store the data source driver plug-in implementation class, and the stored key value is the value obtained by the getHeader method of the data source driver plug-in implementation class; the variable pluginFactories of PluginRegistry is used to store the data source template extension plug-in implementation class, and the stored key value is the value obtained by the getHeader method of the data source template extension plug-in implementation class; when the user starts the console tool module to add a data source, DriverRegistry finds the matching DriverFactory implementation class through the specified protocol header, calls the createDriver method of DriverFactory, creates a driver instance Driver that connects to the database, and calls the createConnection method of Driver to create a database connection instance.

[0054] The system of this embodiment provides a database management system with lightweight characteristics, capable of meeting the graphical management requirements of multi-source databases, and having flexible configuration and high compatibility characteristics. It avoids the cumbersome steps in managing multi-source databases in a hybrid database environment and reduces operation and maintenance costs.

[0055] Embodiment 2:

[0056] The present invention provides a database management method, which manages the database through the system disclosed in Example 1.

[0057] The method comprises the following steps:

[0058] (1) Download the compatible data source driver plug-in and the corresponding data source template extension plug-in;

[0059] (2) Register the data source driver plug-in and data source template extension plug-in in the console tool module;

[0060] (3) Load the registered data source driver plug-in and data source template extension plug-in when the console tool is started to achieve data source integration and management;

[0061] (4) Configure and manage data sources through user interaction through the user interface;

[0062] (5) Based on user input, the configured data source driver plug-in and data source template extension plug-in are used to perform add, delete, modify and query operations on the data source instance.

[0063] The specific operation of step (5) is as follows:

[0064] (5-1) Process user operations as events within the console tool module;

[0065] (5-2) Call the appropriate plug-in configurator and manager to generate command statements for add, delete, modify and query operations;

[0066] (5-3) Send command statements to the connected data source through the established connection to perform operations.

[0067] The present invention has been shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the means in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the protection scope of the present invention.

Claims

1. A database management system, characterized in that: Includes data source driver management module, data source template extension module and console tool module; The data source driver management module is used to maintain the integrated data source driver plug-in; The data source template extension module is used to provide different data source management template plug-ins for the console tool module; The console tool module includes a user interface, a scheduling center and a registration center. It interacts with the outside world through the user interface, supports users to configure and manage data sources, and supports users to add, delete and modify data sources. The scheduling center handles the monitoring of user operation events, manages and schedules data source driver management modules and data source template extension modules, and provides registration and implementation of data source driver plug-ins and data source management template plug-ins through the registration center.

2. The database management system according to claim 1, characterized in that: The data source driver management module supports developers to upload and update data source driver plug-ins, persist data source driver plug-ins in a database, and supports ordinary users to download data source driver plug-ins.

3. The database management system according to claim 1, characterized in that: Data source extensions include processors, configurators, and managers; The manager is used to abstract the add, delete, and modify operations of various instance objects of the data source into corresponding action methods, and encapsulate the statements for operating various instance objects of the data source within the action methods; The configurator is used to provide the graphical interface and interface instantiation scheduling logic required for the manager operation. The configurator defines the Dialog interface, Page interface, Wizard interface and Configure interface. As a developer, the user implements the dialog box Dialog, page Page and wizard Wizard required for each operation according to the specific business, and implements the Configure interface to instantiate the dialog box Dialog, page Page or wizard Wizard; The processor is used to implement the scheduling logic of the configurator and manager, and encapsulate the return results of the manager's action method into commands for processing by the console tool module.

4. The database management system according to claim 1, characterized in that: The registration center defines the Driver interface, DriverFactory interface, Driver interface, Plugin interface and PluginFactory interface. The Driver interface and DriverFactory interface are implemented by the data source driver plug-in, and the Plugin interface and PluginFactory interface are implemented by the data source template extension plug-in. Among them, the DriverFactory and PluginFactory implementation classes need to be registered in the DriverRegistry and PluginRegistry of the console tool module main program through plug-in technology. The variable driverFactories of DriverRegistry is used to store the data source driver plug-in implementation class. The stored key value is the value obtained by the getHeader method of the data source driver plug-in implementation class. The variable pluginFactories of PluginRegistry is used to store the data source template extension plug-in implementation class. The stored key value is the value obtained by the getHeader method of the data source template extension plug-in implementation class. When the user starts the console tool module to add a data source, DriverRegistry finds the matching DriverFactory implementation class through the specified protocol header, calls the createDriver method of DriverFactory, creates a driver instance Driver that connects to the database, and calls the createConnection method of Driver to create a database connection instance.

5. The database management system according to claim 4, characterized in that: The dispatch center includes executors, listeners, and processors; The user interface provides a management console and a data query interface, which are used to encapsulate user operations into events and send them to the dispatch center. After the listener listens to the corresponding event, it calls the page defined in the configurator of the data source template extension plug-in through the processor to display it back to the user. According to the user input, the processor calls the manager in the data source template extension plug-in to obtain the corresponding statement processing command, and submits the statement processing command to the executor. The processor parses the statements for operating various instance objects of the data source from the processing command and submits them to the executor. The executor sends the statement to the corresponding data source through the connection instance of the created managed database to complete this operation.

6. A database management method, characterized in that: The database is managed by a database management system as described in any one of claims 1 to 5.

7. The database management method according to claim 6, characterized in that: The steps include: Download compatible data source driver plug-ins and corresponding data source template extension plug-ins; Register the data source driver plug-in and data source template extension plug-in in the console tool module; Load the registered data source driver plug-in and data source template extension plug-in when the console tool is started to achieve data source integration and management; Configure and manage data sources through user interaction with the user interface; According to user input, data source instance addition, deletion, modification and query operations are performed through the configured data source driver plug-in and data source template extension plug-in.

8. The database management method according to claim 7, characterized in that: According to user input, the data source driver plug-in and data source template extension plug-in are configured to perform add, delete, modify and query operations on the data source instance, including the following steps: Process user actions as events within the console tool module; Call the appropriate plugin configurator and manager to generate command statements for add, delete, modify and query operations; Sends command statements through an established connection to the connected data source to perform operations.

Images