Embedded and general database integrated architecture design method

Abstract

The invention provides an embedded and general database integrated architecture design method, which belongs to the field of embedded and general databases, and is characterized in that a functional plug-in market is established by stripping a database core function and other functions based on an existing general database and enabling the other functions to be plug-in; therefore, an embedded database and a general database can be expanded based on the core function of the database, and a user can purchase and install functional plug-ins as required according to own scenes. A database manufacturer only needs to maintain one code to derive the embedded and general databases, and a customer only needs a batch of operation and maintenance personnel to manage all the embedded and general databases. The edge computing database and the cloud database are isomorphic, so that the edge data can be synchronized and copied to the cloud more easily. And the cloud database can also provide database products purchased by the user according to needs, so that the customer can pay according to needs really.

Description

Technical Field

[0001] The present invention relates to the field of embedded and general databases, and in particular to a method for designing an integrated architecture of embedded and general databases. Background Art

[0002] With the progress of the times and the development of science and technology, 5G technology is becoming more and more popular, the application of the Internet of Things is becoming more and more extensive, and the construction of smart cities is becoming faster and faster. There is an increasing demand for embedded databases, and embedded databases are ushering in unprecedented development opportunities. General databases are the first choice for handling complex data management tasks due to their easy understanding, convenient operation, standardized SQL language, strong transaction processing capabilities, and easy expansion and integration, which has promoted the application and sustainable development of the database industry.

[0003] The development of embedded databases and general databases is mainly as follows: 1. As an important branch of the database field, embedded databases have been widely used in recent years with the development of technologies such as the Internet of Things, mobile computing, and edge computing. This type of database is usually integrated into the application and does not require a separate server. It has the characteristics of small size, fast response speed, and low resource consumption. With the continuous growth of demand in fields such as smart devices and industrial automation systems, embedded databases play an increasingly important role in data storage and management. At the same time, in order to adapt to different application scenarios, embedded databases are also constantly innovating, including supporting unstructured data, improving concurrency performance, and enhancing data security.

[0004] 2. Since its birth in the 1970s, general-purpose databases have become an important branch of computer science. After decades of evolution, its theoretical basis has been increasingly improved and its technology has been continuously innovated. From the initial hierarchical model and network model to the proposal of the relational model, general-purpose databases have dominated with their concise mathematical theory, powerful query functions and extensive support communities. With the emergence of new technologies such as cloud computing and big data, general-purpose databases are adapting to the changes of the times and developing new directions such as distributed, in-memory computing, and columnar storage. They have supported unstructured data, improved concurrency performance, and enhanced data security to meet the growing needs of data processing and security. In the future, general-purpose databases will continue to maintain their development momentum, integrate innovation with emerging technologies, and provide a solid data management foundation for information systems. Summary of the invention

[0005] In order to solve the above technical problems, the present invention provides an integrated architecture design method for embedded and general databases, which separates the core functions of the general database from other functions and disassembles other functions into functional plug-ins. The advantage of this is that the basic functions are the core functions of the database, which are built-in no matter what the circumstances are, and other functions can be selected as needed. The core functions of the database are very small and can be installed on any device. If necessary, the database functions can be made more powerful by installing functional plug-ins to adapt to more application scenarios.

[0006] The technical solution of the present invention is: A design method for integrated architecture of embedded and general databases. Based on the core functions of the database, an embedded database can be formed by installing embedded related plug-ins, and a general database can be formed by installing general database related plug-ins; After the database is successfully installed, the relevant equipment can connect to the database plug-in market online to pull and install database function plug-ins in the database to expand more database functions. Unnecessary function plug-ins can also be uninstalled at any time.

[0007] Furthermore, Embedded databases can be installed on embedded devices, and general databases can be installed on servers.

[0008] Furthermore, The database core functions provide a mechanism for functional extension.

[0009] Specific extension statements are built-in functions of the database core functions, which extend more object types, data types, operators, functions, aggregations, access methods, and index methods; in 1) Extended object types. Each object type in the core database function provides syntax for creation, modification, and deletion. These syntaxes are operations for maintaining system tables related to the object type. The object type syntax is parsed and processed by the plug-in, and the CREATE ..., ALTER ... and DROP ... statements are completely passed to the corresponding object type processing function for further parsing. The system table is maintained based on the detailed information further parsed. After the object type is expanded, the syntax of the expanded object type is used to create, modify, and delete related objects. During the syntax parsing phase of the database core function, it will be found that the statement is an operation to create, modify, and delete objects. Then, it will search the object type system table to see if there is a related object type. After finding the object type, it will directly call the object type's create operation to create the object, call the object type's modify operation to modify the object, and call the object's delete operation to delete the object. After creating an object instance, the purpose of using the object is achieved by rewriting related functions.

[0010] The extension of other functions is realized through the extension functions provided by the database. In the process of realizing the core functions of the database, all functions are considered to come from metadata, and all operations are obtained from metadata. In this way, more functions can be expanded by simply inserting more records in the metadata. The core functions of the database have built-in SQL extension and maintenance interfaces for database objects, data types, operators, aggregations, and access methods. Users can insert, modify and delete corresponding records in the system table through SQL statements, thereby realizing the functions of creating, modifying and deleting extensions.

[0011] Furthermore, Develop, package and publish functional plug-ins. Database functional plug-ins include plug-in control files, plug-in-related SQL scripts and plug-in-related dynamic link libraries. When developing functional plug-ins, package these functions into an executable program or a Windows executable installation package, using the same organization method for the same platform. The packaged functional plug-ins are published in the plug-in market, and the plug-in functions and instructions for use are explained during publication.

[0012] Develop functional plug-ins Develop various functional plug-ins using the basic functions, basic core functions and extended functions provided by the database. When developing plug-ins, organize plug-in related files in the same directory, provide Makefile, and compile through make; Compilation is to compile the code written in C language into a dynamic link library. The code also provides a SQL script to create the data types, functions, aggregations, and operators that the functional plug-in depends on. The code also provides a plug-in control file, which records the version number of the functional plug-in, the dynamic link library path, and the installation mode information. Packaging plugins The Makefile of the code provides a package target, and the plug-in is packaged into an executable program through make package. After the executable program is run, the packaged files are unzipped and installed to the corresponding directory of the database. At the same time, the owner and permissions of the relevant files are modified, and then the plug-in creation operation is executed to install the plug-in into the database. When compiling and packaging, executable packages for various platforms are printed to ensure that the plug-in can be installed on any platform.

[0013] Release functional plugin Upload the functional plug-in to the plug-in market. The functional plug-in provides executable installation packages for each platform and publishes them together with instructions and usage documents.

[0014] Furthermore, Database plugin market Provide plug-ins with various functions. The function plug-ins support any platform supported by the database version. Users can choose to download and install plug-ins according to their own environment, and can also perform related plug-in function management in the database; The plug-in management and installation function is provided in the database client tool. The specific syntax is as follows: 1) Plugin search When the database can be connected to the plugin market, search for related plugins in the plugin market according to the plugin name and list them to the user: 2) Plug-in download When the database can connect to the plugin market, directly download the user-specified plugin to the local database software directory: 3) Plugin installation Install the downloaded plug-in directly into the database by executing SQL statements: 4) Plugin upgrade If the downloaded plug-in is newer than the plug-in installed in the database, you can execute SQL statements to update the installed plug-in: 5) Uninstall plugin The plug-in can be uninstalled directly through SQL statements when it is no longer needed.

[0015] Going further, The plug-in market provides a WEB interface access method to facilitate users to search and install functional plug-ins as needed.

[0016] The beneficial effects of the present invention are The present invention allows database manufacturers to provide embedded database and general database products at the same time without investing more R&D personnel, and allows the same group of database operation and maintenance managers of customers to maintain embedded and general databases at the same time without spending more time on learning and training.

[0017] Database products based on the integrated architecture of embedded database and general database can be either efficient and compact embedded databases or general databases that support high concurrency and comprehensive functions. By deeply integrating embedded database and general database technologies, this architecture not only improves the stability of the database kernel, but also enhances the scalability, usability and maintainability of the system. This design approach enables developers to flexibly select or combine embedded and general database functions according to specific application scenarios, thereby optimizing system resource utilization.

[0018] Customers can be attracted through the database plug-in market, and the plug-in market functions can be kept under constant attention to increase customer attention. At the same time, customers can also develop plug-ins for specific scenarios and sell them in the plug-in market to increase customer enthusiasm for using databases. The function plug-in market is very similar to various APP markets and has been verified in many other industries. Database function plug-ins allow users to purchase function plug-ins on demand, reducing customer usage costs and greatly promoting the cloud database market.

[0019] In short, this integrated architecture design approach brings many benefits to the company and can promote the innovation and development of related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic diagram of the overall structure of the present invention; Figure 2 It is a schematic diagram of the structure of the core functions of the database; Figure 3 is a functional schematic diagram of an extended synonym object type; Figure 4 This is a schematic diagram of the database plug-in market. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0022] The integration of embedded database and general database can achieve complementary optimization of performance and function. This combination reduces system complexity, improves response speed, and reduces resource usage, which is especially suitable for resource-constrained edge computing environments. At the same time, it ensures data consistency and reliability, meeting the needs of complex business scenarios. The simplified deployment and maintenance process reduces operation and maintenance costs, while good compatibility and scalability support the smooth evolution and upgrading of technology, bringing long-term competitive advantages to enterprises. The integration of embedded database and general database can greatly reduce the pressure of cloud computing, and can also facilitate the real-time synchronization of edge computing results to the cloud.

[0023] Currently, embedded databases and general-purpose databases are completely different product forms. For database manufacturers, developing both embedded databases and general-purpose databases requires more research and development, and for customers, more database operation and maintenance personnel are needed. Designing these two types of databases into an integrated architecture can save a lot of costs for both database manufacturers and customers.

[0024] After so many years of development, general databases have developed many functions that embedded databases do not support. The integration of embedded and general databases can accelerate the development of embedded databases. Embedded databases can quickly make up for shortcomings in functions, performance, and security. General databases can be quickly tailored to become embedded databases that meet needs.

[0025] By separating the core functions of the general database from other functions and turning other functions into plug-ins, it is easy to develop an embedded database based on the general database. At the same time, a full-featured general database can be expanded based on the embedded database through plug-ins.

[0026] Develop a remote installation tool that can easily install embedded databases. The installation tool also provides customized installation and uninstallation plug-in functions, which makes it easier for users to manage embedded databases and general database support functions. At the same time, an online plug-in market is established, so that database plug-ins can be purchased and installed in the market, so that users can truly purchase and use them on demand. The present invention provides an integrated architecture design method for embedded and general databases. Based on the existing general database, the core functions and other functions of the database are stripped away, and other functions are plug-inized to establish a functional plug-in market. In this way, embedded databases and general databases can be expanded based on the core functions of the database, and users can purchase and install functional plug-ins on demand according to their own scenarios. Database manufacturers only need to maintain a copy of the code to derive embedded and general databases, and customers only need a group of operation and maintenance personnel to manage all embedded and general databases. The edge computing database and the cloud database are isomorphic, and it is easier to synchronize and copy edge data to the cloud. The cloud database can also provide users with database products that can be purchased on demand, truly allowing customers to pay on demand.

[0027] The overall structure of technologies and components involved in the integrated architecture of embedded and general databases is as follows: Figure 1 shown.

[0028] The entire integrated architecture is based on the core functions of the database. An embedded database can be formed by installing embedded-related plug-ins, and a general database can be formed by installing general database-related plug-ins. Embedded databases can be installed on embedded devices, and general databases can be installed on servers. These differences are determined during the installation process, and there is no difference in the database core itself. In other words, it is no problem to install an embedded database on a server, but the installed plug-ins are different. Because the memory of embedded devices is very small and the storage space is limited, some plug-ins that occupy a lot of memory and disk cannot be installed on embedded devices, otherwise the memory and storage space of the embedded device will be insufficient, resulting in the database being unable to run stably.

[0029] After the database is successfully installed, all major related devices with Internet access can connect to the database plug-in market, and database function plug-ins can be easily pulled and installed in the database to expand more database functions. Unnecessary function plug-ins can also be uninstalled at any time.

[0030] 1. Database core functions There are some indispensable functions in the database. These functions are the foundation of the database and are called database core functions. In the integrated architecture, the core functions must be built into the database so that the database can be installed and started normally. The database core functions mainly include: Basic data types: data types used by system tables, which must be built into the database Basic operators: Operators related to basic data types must be built into the system, otherwise the database cannot run Basic functions: functions related to basic data types and operators, as well as functions required by the database Basic aggregation: Aggregation functions related to basic data types to facilitate users to directly use these basic data types Transaction processing: The implementation of transactions is relatively complex and difficult to be plug-in. It should be implemented in the core functions of the database. Memory management: The memory in the database will be managed uniformly to reduce the interaction time with the operating system and improve database performance. Exception handling: When an exception occurs in the database, resources should be released in a timely manner and the exception should be reported to the client. Database management: Database instances need to manage databases, and database instance startup requires a database management module Schema management: Database search objects are based on schema management. Any object needs to be searched in the schema. Table access method: Database system tables also need to be managed and accessed, and the database should have at least one built-in table access method Index access method: Database system tables also use indexes, and the database should have at least one built-in index access method View management: The database needs to have some system views built in to facilitate users to access some system table information Cache management: Database caching not only improves performance, but also controls database memory usage Log management: Log files are the core function of the database, and kernel-related operations also rely on log management functions. File management: The main function of the database is to manage data. Data must be stored on disk through file management. Basic functions: In addition, the database also has some necessary basic functions, which should also be built into the core, such as syntax parsing, optimizer, and executor.

[0031] In addition to these basic functions, the core functions of the database must also provide a mechanism for function extension, such as extending system tables, extending data types, extending functions, extending aggregations, extending operators, extending access methods, and extending index methods. Any function of the database can be considered as an operation on certain system tables. For example, extending a data type can be considered as inserting a record in the data type metadata. However, in order to insert this record, it is necessary to implement the input and output functions and the sending and receiving functions of the data type that this record depends on. This requires first creating the functions that the data type depends on, and then inserting a record in the data type metadata to extend a data type. The data type needs to perform operations such as addition, subtraction, multiplication, and division, needs to compare sizes, needs to calculate aggregation values, needs to be sorted, needs to calculate hash values, and needs to be converted with other types. This requires the expansion of operators, aggregations, and various functions based on the extended data type.

[0032] The structure of the database core functions of the entire embedded and general database integrated architecture is as follows Figure 2 shown.

[0033] Specific extension statements are built-in functions of the database core functions, which can be used to expand more object types, data types, operators, functions, aggregations, access methods, and index methods. This integrated architecture can even expand more system tables and more new syntax. The extension language is a typical example of expanding new syntax.

[0034] 1.1. Extended object type Each object type in the core functions of the database provides syntax for creation, modification, and deletion. These syntaxes can be considered as operations for maintaining system tables related to the object type. However, the syntax for creating each object type is quite different, so the syntax of the object type can be parsed and processed by the plug-in. Statements such as CREATE..., ALTER... and DROP... can be passed completely to the processing function of the corresponding object type for further parsing, and the system table can be maintained based on the detailed information further parsed.

[0035] like Figure 3 As shown in the figure, taking the function of extending the synonym object type as an example, the overall logic of the extended object type function is explained: The main execution flow of the extended object type: The user creates objects that depend on the object type. The figure shows the creation, modification, and deletion functions of synonym dependencies. Creation function of object type Modification functions for object types Delete function of object type … The user creates an object type. In the figure, the user uses the CREATE OBJECT syntax to create the SYNONYM object type. Create system tables related to object types. Each user object type is often managed by a system table. You need to create a system table for the object type during the object type creation process. If the object type does not require a system table, do not create one. Insert the created object into the object type metadata After the object type is extended, the relevant objects can be created, modified and deleted through the syntax of the extended object type. During the syntax parsing stage of the database core function, it will be found that the statement is an operation to create, modify and delete objects, and then it will search the object type system table to see if there is a relevant object type. After finding the object type, it will directly call the object type's create operation to create the object, call the object type's modify operation to modify the object, and call the object's delete operation to delete the object.

[0036] Taking the synonyms in the figure as an example, you can execute the following statements to maintain synonyms: Create a synonym: CREATE SYNONYM synonym_name FOR object_name; The syntax for creating synonyms is determined by the CreateSynonym function registered by CREATE OBJECT, so that users can completely customize the syntax for creating synonyms.

[0037] Modify synonym: ALTER SYNONYM synonym_name OWNER TO new_owner; The syntax for modifying synonyms is determined by the AlterSynonym function registered by CREATE OBJECT, so that users can completely customize the syntax for modifying objects, and can also expand more ALTER SYNONYM syntax, such as modifying the object namespace, object name, namespace or name of the synonym.

[0038] Delete a synonym: DROP SYNONYM synonym_name; The syntax for dropping a synonym is determined by the DropSynonym function registered by CREATE OBJECT, so that users can completely customize the syntax for dropping objects.

[0039] After creating an object instance, you can rewrite related functions to achieve the purpose of using the object. Take synonyms as an example. If you need to use a function to find an object in the database, you only need to rewrite the object search function. In the rewritten search function, you can first search in the same way as before. If the object is not found, search for the object in the synonym system table, and then you can use the created synonym. You can also specify the function to be used directly through some attributes of the object when creating a synonym object, so that the database can use the newly created object.

[0040] 1.2. Expand other functions Other functions can be extended through the extended functions provided by the database. In the process of implementing the core functions of the database, all functions can be considered to come from metadata, and all operations are obtained from metadata. In this way, more functions can be extended by simply inserting more records in the metadata. In order to facilitate expansion, the core functions of the database have built-in SQL extension and maintenance interfaces such as database objects, data types, operators, aggregations, and access methods.

[0041] These extended functions essentially provide a set of SQL methods for maintaining related system tables. Users can insert, modify, and delete corresponding records in the system tables through SQL statements, thereby realizing the functions of creating, modifying, and deleting extensions.

[0042] 2. Develop packaging and publishing functional plug-ins The database function plug-in is a complete function implementation, mainly including the plug-in control file, plug-in-related SQL scripts and plug-in-related dynamic link libraries. In order to facilitate the release of the function plug-in to the plug-in market, when developing the function plug-in, it is best to package all these functions into an executable program, such as a runable file on Linux, or an executable installation package on Windows, etc. Different platforms may have different organizational methods. For the sake of simple maintenance, the same platform uses the same organizational method. The packaged function plug-in can be released in the plug-in market. When publishing, the function and usage instructions of the plug-in need to be explained: 2.1. Develop functional plug-ins Using the basic functions, basic core functions and extended functions provided by the database, various functional plug-ins can be developed, such as data types, compatible functions and database objects. When developing a plug-in, you need to organize the plug-in related files in the same directory and provide a Makefile, which can be compiled through make. Compilation is to compile the code written in C language into a dynamic link library. The code should also provide a SQL script to create data types, functions, aggregations, operators and other objects that the functional plug-in depends on. The code should also provide a plug-in control file, which can record the version number of the functional plug-in, the dynamic link library path and the installation mode.

[0043] 2.2. Packaging function plug-in The Makefile of the code should also provide a package target, which can be used to package the plug-in into an executable program. After the executable program is run, the packaged files will be unzipped and installed to the corresponding directory of the database. At the same time, the owner and permissions of the relevant files will be modified, and then the plug-in creation operation will be executed to install the plug-in into the database. When compiling and packaging, it is best to be able to print executable packages for various platforms to ensure that the plug-in can be installed on any platform.

[0044] 2.3. Release functional plug-ins Upload the functional plug-in to the plug-in market. The functional plug-in should provide executable installation packages for each platform and provide detailed instructions and usage documents for external release.

[0045] 3. Database plug-in market The database plug-in market provides plug-ins with various functions. Function plug-ins support any platform supported by the database version. Users can choose to download and install plug-ins according to their own environment, and can also perform related plug-in function management in the database. The database plug-in management function is easier to use, and you can choose the appropriate plug-in installation package and install it according to the user's environment.

[0046] A convenient plug-in management and installation function is provided in the database client tool. The specific syntax is as follows: 1) Plugin Search When the database can be connected to the plugin market, search for related plugins in the plugin market according to the plugin name and list them to the user: For example: EXTENSION SEARCH<ext_name> ; 2) Download plugins When the database can connect to the plugin market, directly download the user-specified plugin to the local database software directory: For example: EXTENSION PULL<ext_name> ; 3) Plug-in installation You can install the downloaded plug-in directly into the database by executing SQL statements: For example: EXTENSION INSTALL<ext_name> ; 4) Plugin upgrade If the downloaded plug-in is newer than the plug-in already installed in the database, you can execute SQL statements to update the installed plug-in: For example: EXTENSION UPGRADE<ext_name> ; 5) Uninstall plugin The plugin can be uninstalled directly through SQL statements when it is no longer needed: For example: EXTENSION UNINSTALL<ext_name> ; The plug-in market should also provide access to the WEB interface, which can facilitate users to search and install functional plug-ins as needed.

[0047] The above description is only a preferred embodiment of the present invention, which is only used to illustrate the technical solution of the present invention, and is not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for designing an integrated architecture of an embedded and general database, characterized in that: Based on the core functions of the database, an embedded database can be formed by installing embedded related plug-ins, and a general database can be formed by installing general database related plug-ins; After the database is successfully installed, the relevant equipment can connect to the database plug-in market online to pull and install database function plug-ins in the database to expand more database functions. Unnecessary function plug-ins can also be uninstalled at any time.

2. The method according to claim 1, characterized in that: Embedded databases can be installed on embedded devices, and general databases can be installed on servers.

3. The method according to claim 1, characterized in that The database core functions provide a mechanism for functional extension.

4. The method according to claim 3, characterized in that Specific extension statements are built-in functions of the database core functions, which extend more object types, data types, operators, functions, aggregations, access methods, and index methods; in 1) Extended object types. Each object type in the core database function provides syntax for creation, modification, and deletion. These syntaxes are operations for maintaining system tables related to the object type. The syntax of the object type is parsed and processed by the plug-in, and the CREATE..., ALTER... and DROP... statements are completely passed to the processing function of the corresponding object type for further parsing. The system table is maintained based on the detailed information further parsed. After the object type is expanded, the syntax of the expanded object type is used to create, modify, and delete related objects. During the syntax parsing phase of the database core function, it will be found that the statement is an operation to create, modify, and delete objects. Then, the object type system table will be searched for the existence of the related object type. After the object type is found, the object type's create operation will be directly called to create the object, the object type's modify operation will be called to modify the object, and the object's delete operation will be called to delete the object. After creating an object instance, the purpose of using the object is achieved by rewriting related functions.

5. The method according to claim 4, characterized in that The extension of other functions is realized through the extension functions provided by the database. In the process of realizing the core functions of the database, all functions are considered to come from metadata, and all operations are obtained from metadata. In this way, more functions can be expanded by simply inserting more records in the metadata. The core functions of the database have built-in SQL extension and maintenance interfaces for database objects, data types, operators, aggregations, and access methods. Users can insert, modify and delete corresponding records in the system table through SQL statements, thereby realizing the functions of creating, modifying and deleting extensions.

6. The method according to claim 1, characterized in that Develop, package and publish functional plug-ins. Database functional plug-ins include plug-in control files, plug-in-related SQL scripts and dynamic link libraries involved in the plug-in. When developing functional plug-ins, package these functions into an executable program or a Windows executable installation package, and use the same organization method for the same platform; the packaged functional plug-ins are published in the plug-in market, and the functions and instructions for use of the plug-ins are described during the publication.

7. The method according to claim 6, characterized in that Develop functional plug-ins Develop various functional plug-ins using the basic functions, basic core functions and extended functions provided by the database. When developing plug-ins, organize plug-in related files in the same directory, provide Makefile, and compile through make; Compilation is to compile the code written in C language into a dynamic link library. The code also provides a SQL script to create the data types, functions, aggregations, and operators that the functional plug-in depends on. The code also provides a plug-in control file, which records the version number of the functional plug-in, the dynamic link library path, and the installation mode information. Packaging plugins The Makefile of the code provides a package target, and the plug-in is packaged into an executable program through make package. After the executable program runs, the packaged files are decompressed and installed to the corresponding directory of the database. At the same time, the owner and permissions of the relevant files are modified, and then the plug-in creation operation is executed to install the plug-in into the database. Release functional plugin Upload the functional plug-in to the plug-in market. The functional plug-in provides executable installation packages for each platform and publishes them together with instructions and usage documents.

8. The method according to claim 7, characterized in that When compiling and packaging, executable packages for various platforms are generated to ensure that the plug-in can be installed on any platform.

9. The method according to claim 1, characterized in that: Database plugin market Provides plug-ins with various functions. Function plug-ins support any platform supported by the database version. Users can choose to download and install plug-ins according to their own environment, and can also perform related plug-in function management in the database; The plug-in management and installation function is provided in the database client tool. The specific syntax is as follows: 1) Plugin Search When the database can be connected to the plugin market, search for related plugins in the plugin market according to the plugin name and list them to the user: 2) Download plugins When the database can connect to the plugin market, directly download the user-specified plugin to the local database software directory: 3) Plug-in installation Install the downloaded plug-in directly into the database by executing SQL statements: 4) Plugin upgrade If the downloaded plug-in is newer than the plug-in installed in the database, you can execute SQL statements to update the installed plug-in: 5) Uninstall plugin The plug-in can be uninstalled directly through SQL statements when it is no longer needed.

10. The method according to claim 9, characterized in that The plug-in market provides a WEB interface access method to facilitate users to search and install functional plug-ins as needed.

Images