WO2024060956A1

WO2024060956A1 - Hybrid database management method and apparatus, hybrid database, and electronic device

Info

Publication number: WO2024060956A1
Application number: PCT/CN2023/116095
Authority: WO
Inventors: 高昆仑; 乔贵邠; 赵保华; 陈国宝; 张亮; 周飞; 林剑超
Original assignee: 国网智能电网研究院有限公司; 方图数据(北京)软件股份有限公司
Priority date: 2022-09-21
Filing date: 2023-08-31
Publication date: 2024-03-28
Also published as: CN115269561A; CN115269561B

Abstract

The present application provides a hybrid database management method and apparatus, a hybrid database, and an electronic device. The method comprises: on the basis of a shared connection to a hybrid database server, establishing communications with databases comprised in a hybrid database, so as to enter a first database access environment or a second database access environment, the hybrid database comprising a first database and a second database; and when the second database needs to be accessed in the first database access environment of the hybrid database, calling a preset second database connection interface in an interface layer of the first database, so as to connect to and access the second database. According to the method provided by the solution, the second database connection interface is called in the first database access environment so as to quickly switch to access the second database, thereby improving the application efficiency of the hybrid database.

Description

A hybrid database management method, device, hybrid database and electronic equipment

Cross-references to related applications

The present invention is based on a Chinese patent application with application number 202211148362.6 and a filing date of September 21, 2022, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference into the present invention.

Technical field

The present application relates to the technical field of database management, and in particular to a hybrid database management method, device, hybrid database and electronic device.

Background technique

As users' requirements for the intelligence of current data management systems increase, hybrid database products have been widely used, such as hybrid databases composed of graph databases and relational databases.

Hybrid databases in the prior art usually perform mode isolation according to database type at the interface level. Users need to access the corresponding type of database in the specified mode. When the user needs to access other types of databases next, they need to change the database connection and switch to the corresponding mode. The operation process is relatively cumbersome, which reduces the application efficiency of the hybrid database.

Summary of the invention

This application provides a hybrid database management method, device, hybrid database and electronic equipment to solve the shortcomings of the existing technology, such as reducing the application efficiency of the hybrid database.

The first aspect of this application provides a hybrid database management method, including:

Based on the shared connection of the hybrid database server, establish communication with each database included in the hybrid database to enter the first database access environment or the second database access environment; wherein the hybrid database includes the first database and the second database;

When it is necessary to access the second database in the first database access environment of the hybrid database, the preset second database connection interface is called at the interface layer of the first database to connect and access the second database.

In one embodiment, calling the preset second database connection interface at the interface layer of the first database includes:

Call the first database business interface at the interface layer of the first database;

Send a preset second database connection interface calling instruction to the first database business interface to convert the currently called first database business interface into a preset second database connection interface.

In one embodiment, the method further includes:

Unified management of all context data generated when accessing the first database and the second database to share all context data;

Wherein, the context data includes at least session context data, user security authority context data and database transaction context data.

In one embodiment, the method further includes:

Based on the preset second database connection interface, send a second database service to the second database to obtain the corresponding second database service processing result;

Wherein, the second database service is processed based on the second database data processing engine.

In one embodiment, the method further includes:

When it is necessary to access the first database in the first database access environment of the hybrid database, calling the preset first database business interface in the interface layer of the first database;

Based on the preset first database service interface, sending the first database service to the first database to obtain the corresponding first database service processing result;

Wherein, the first database service is processed based on the first database data processing engine.

In one embodiment, the first database is a graph database, and the second database is a relational database;

The first database access environment is a data query environment using Gremlin graph query language, the second database access environment is a data query environment using JDBC relational query language, the first database business interface is a Gremlin business interface, and the The second database connection interface is a JDBC connection interface.

The second aspect of this application provides a hybrid database management device, including:

The first management part is configured to establish communication with each database included in the hybrid database based on the shared connection of the hybrid database server to enter the first database access environment or the second database access environment; wherein the hybrid database includes the first database and the second database;

The second management part is configured to call the preset second database connection interface at the interface layer of the first database when it is necessary to access the second database in the first database access environment of the hybrid database to connect and Access the second database.

In one embodiment, the second management part is further configured to:

A preset second database connection interface calling instruction is sent to the first database service interface to convert the currently called first database service interface into a preset second database connection interface.

In one embodiment, the device further includes:

A third management part configured to uniformly manage all context data generated when accessing the first database and the second database to share all context data;

In one embodiment, the third management part is further configured to:

Based on the preset first database service interface, send a first database service to the first database to obtain the corresponding first database service processing result;

The third aspect of this application provides a hybrid database, a first database, a second database and a hybrid database management device as described in the second aspect and various possible designs of the second aspect;

The interface layer of the first database has a preset second database connection interface;

The interface layer of the second database has a preset first database connection interface;

The hybrid database management adopts the hybrid database management method described in the first aspect and various possible designs of the first aspect to manage the first database and the second database.

A fourth aspect of the present application provides an electronic device, including: at least one processor and a memory;

The memory stores computer execution instructions;

The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the method described in the above first aspect and various possible designs of the first aspect.

A fifth aspect of the present application provides a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When a processor executes the computer-executable instructions, Methods as described in the first aspect and various possible designs of the first aspect.

The technical solution of this application has the following advantages:

The present application provides a hybrid database management method, device, hybrid database and electronic device, the method comprising: establishing communication with each database included in the hybrid database based on a shared connection of the hybrid database server to enter a first database access environment or a second database access environment; wherein the hybrid database comprises a first database and a second database; when the second database needs to be accessed in the first database access environment of the hybrid database, calling a preset second database connection interface at the interface layer of the first database to connect to and access the second database. The method provided by the above scheme improves the application efficiency of the hybrid database by implementing the call of the second database connection interface in the first database access environment to quickly switch to access the second database.

Description of drawings

In order to more clearly explain the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

FIG1 is a schematic diagram of a flow chart of a hybrid database management method provided in an embodiment of the present application;

Figure 2 is a schematic structural diagram of a hybrid database management device provided by an embodiment of the present application;

Figure 3 is a schematic structural diagram of a hybrid database provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Through the above-mentioned drawings, clear embodiments of the present application have been shown, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the present application to those skilled in the art with reference to specific embodiments.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments These are part of the embodiments of this application, but not all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

Furthermore, the terms “first”, “second”, etc. are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. In the description of the following embodiments, "plurality" means two or more, unless otherwise explicitly and specifically limited.

There is no unified and standardized query language among the existing graph query languages. The most widely used and typical mainstream languages include Gremlin and Cypher. Gremlin is based on Groovy, but has many language variants, allowing developers to write queries natively in programming languages such as Java and Python. It contains both imperative and declarative semantics, and can easily express the logic of graph traversal, so it is adopted by many graph database systems.

A relational database is based on the relational data model and uses mathematical concepts and methods such as set algebra to process data. Various entities in the real world and various connections between entities can be represented by relational models.

The query language of relational database is SQL language, which is Structured Query Language (Structured Query Language), which is an advanced non-procedural programming language.

Java Database Connectivity (JDBC for short) is an application programming interface in the Java language that is used to standardize how client programs access databases. It provides methods such as querying and updating data in relational databases.

In the application process of graph databases, existing intelligent applications have more and more requirements for hybrid applications of data in other modes. That is, in the same application system, when using graph databases, other database types, such as document databases, relational databases, etc., are also used, showing the characteristics of a "hybrid" mode.

However, current hybrid databases usually implement mode isolation according to database types at the interface level. Users need to access the corresponding type of database in the specified mode. When the user needs to access other types of databases, they need to switch to the corresponding mode. The operation process is relatively complicated. It is cumbersome and reduces the application efficiency of hybrid databases.

In response to the above problems, the hybrid database management method, device, hybrid database and electronic equipment provided by the embodiments of the present application establish communication with each database included in the hybrid database through a shared connection based on the hybrid database server to enter the first database access environment. Or a second database access environment; wherein the hybrid database includes a first database and a second database; when it is necessary to access the second database in the first database access environment of the hybrid database, the preset third database is called at the interface layer of the first database. The second database connection interface is used to connect and access the second database. The method provided by the above solution realizes the invocation of the second database connection interface in the first database access environment to quickly switch to access the second database, thereby improving the application efficiency of the hybrid database.

The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will be described below with reference to the accompanying drawings.

The embodiment of the present application provides a hybrid database management method, which is used to manage the user's access to the hybrid database, so as to improve the application efficiency of the hybrid database. The execution subject of the embodiment of this application is an electronic device that can be used as a hybrid database client, such as a server, a desktop computer, a notebook computer, Tablets and other electronic devices.

As shown in Figure 1, it is a schematic flow chart of a hybrid database management method provided by an embodiment of the present application. The method includes:

Step 101: Based on the shared connection of the hybrid database server, establish communication with each database included in the hybrid database to enter the first database access environment or the second database access environment.

The hybrid database includes a first database and a second database. The first database may be a graph database, and the second database may be a relational database.

It should be noted that when the first database and the second database are deployed on different servers, the shared connection of the hybrid database server can be the IP address of the preset intermediate server, and the preset intermediate server is connected to the first database server and the third database server respectively. The two database servers establish a communication connection. When the first database and the second database are deployed on the same server, the shared connection of the hybrid database server is the IP address of the server.

In one embodiment, the client of the hybrid database can simultaneously establish communication connections with the first database and the second database based on the shared connection of the hybrid database server, so that the client can enter the first database access environment based on the shared connection or Second database access environment.

For example, when the first database is a graph database and the second database is a relational database, the first database access environment may be a data query environment using the Gremlin graph query language, and the second database access environment may be a JDBC relational database. In the data query environment of the query language, the first database business interface may be a Gremlin business interface, and the second database connection interface may be a JDBC connection interface.

It should be further explained that the hybrid database management method provided by the embodiment of the present application realizes the connection and sharing of the running environment of the first database and the second database. The first database instance and the second database instance are different from the perspective of user-side applications. The physical connection is shared and reused, and the physical connection is the shared connection of the hybrid database server.

Step 102: When it is necessary to access the second database in the first database access environment of the hybrid database, call the preset second database connection interface in the interface layer of the first database to connect to and access the second database.

In one embodiment, the user can call the preset second database connection interface in the interface layer of the first database based on instructions written in the Gremlin language in the first database access environment.

Among them, the interface layer of the first database may include several business interfaces (transaction interface), and at the same time be expanded with a second database connection interface (JDBC Connection interface) suitable for the second database.

Based on the above embodiments, as an implementable method, in one embodiment, calling the preset second database connection interface in the interface layer of the first database includes:

Step 1021: Call the first database business interface at the interface layer of the first database;

Step 1022: Send a preset second database connection interface call instruction to the first database business interface to convert the currently called first database business interface into the preset second database connection interface.

For example, when the first database is a graph database and the second database is a relational database, the preset second database connection interface calling instruction may be Connection conn=graph.tx().getRdbConnection().

In one embodiment, the first database service interface can be obtained first, the first database service interface instance of the first database instance can be obtained based on the first database service interface, and then the preset third database service interface instance can be introduced into the first database service interface instance. The second database connection interface calls instructions to convert the currently called first database business interface into a preset second database connection interface.

Among them, the preset second database connection interface obtained through interface conversion in the embodiment of this application conforms to the connection interface specification of the second database, such as the Connection interface specification of JDBC. JDBC Statement or PreparedStatement can be created, and these Statements can be used. The interface performs query or update operations, or obtains the ResultSet of query results. The Statement/PreparedStatement/ResultSet here all comply with the JDBC interface specification.

In one embodiment, when the first database is a graph database and the second database is a relational database, the user can obtain the database transaction on the graph data side through the aforementioned graph.tx() to control the database transaction; By obtaining the graph instance (graph database instance), the operation interface (such as Traversal, Computing, etc.) on the graph data side is obtained for operation. The client can obtain the transaction control operation interface on the relational data side through the aforementioned Connection interface, and the operation interface executed in SQL language to perform relational data operations.

In one embodiment, all context data generated when accessing the first database and the second database can also be managed uniformly to share all context data.

The context data includes at least session context data, user security permission context data and database transaction context data.

In one embodiment, since the first database and the second database realize the sharing of database transaction context data, whether the first database operation interface or the second database operation interface starts a database transaction (either automatically or manually), The initial database transaction sharing; whether it is the first database operation interface or the second database operation interface, when the transaction operation is submitted, the database transaction operations of the first database and the second database that share the database transaction will be operated; regardless of the first database operation interface Or when the second database operation interface rolls back the transaction operation, the database transaction operations of the first database and the second database that share the database transaction will be rolled back; the relevant characteristics of the database transactions of the first database and the second database such as isolation level, transaction IDs etc. will also be shared.

Based on the above embodiment, as an implementable manner, in one embodiment, the method further includes:

Step 301: Based on the preset second database connection interface, send the second database service to the second database to obtain the corresponding second database service processing result.

It should be noted that in order to improve the data processing efficiency of the hybrid database, the hybrid database can support OLAP+OLTP transaction management at the same time with a unified transaction management mechanism in the data processing core. Data of different database types can be processed separately by different data processing engines. Processing, in order to achieve a hybrid operating environment of different engines that share the data operating environment.

In one embodiment, when the client accesses the first database or the second database based on the hybrid database management method provided in the above embodiment, the server of the first database or the second database requests the context from the same user and the same Session. The first database and the second database will be in the same context running environment such as Session, database transactions, user permissions, etc., so their data processing core can support OLTP+OLAP transaction management at the same time with a unified transaction management mechanism.

Correspondingly, in one embodiment, when it is necessary to access the first database in the first database access environment of the hybrid database, the preset first database business interface can be called at the interface layer of the first database; based on the preset third database A database service interface sends the first database service to the first database to obtain the corresponding first database service processing result.

In one embodiment, when the first database is a graph database and the second database is a relational database, graph data operations are performed by a graph data processing engine, that is, there is a language processing based on Gremlin language parsing and execution to drive a A graph data processing engine characterized by point and edge data to implement graph database business processing and obtain corresponding graph database business processing results. Relational data operations are performed by a relational processing engine, that is, there is a language processing based on SQL language parsing and execution to drive a relationship characterized by row tables and associated data between tables (that is, entities and a collection of relationships between entities). A data processing engine to implement relational database business processing and obtain corresponding relational database business processing results.

Among them, by introducing the data processing engine of each database to process the business of each database in parallel, the business processing efficiency of the hybrid database is improved. Moreover, different processing engines can provide features that comply with query language specifications for different types of data (such as graphs and relational data).

The hybrid database management method provided by the embodiment of the present application establishes communication with each database included in the hybrid database through a shared connection based on the hybrid database server to enter the first database access environment or the second database access environment; wherein the hybrid database includes The first database and the second database; when it is necessary to access the second database in the first database access environment of the mixed database, The preset second database connection interface is called at the interface layer of the first database to connect to and access the second database. The method provided by the above solution realizes the invocation of the second database connection interface in the first database access environment to quickly switch to access the second database, thereby improving the application efficiency of the hybrid database. Moreover, by introducing the data processing engine of each database to process the business of each database in parallel, the business processing efficiency of the hybrid database is improved.

The embodiment of the present application provides a hybrid database management device, used to execute the hybrid database management method provided in the above embodiment.

As shown in Figure 2, it is a schematic structural diagram of a hybrid database management device provided by an embodiment of the present application. The hybrid database management device 20 includes: a first management part 201 and a second management part 202.

Among them, the first management part 201 is configured to establish communication with each database included in the hybrid database based on the shared connection of the hybrid database server to enter the first database access environment or the second database access environment; wherein the hybrid database includes a first database and a second database; the second management part 202 is configured to call a preset second database connection interface at the interface layer of the first database to connect to and access the second database when the second database needs to be accessed under the first database access environment of the hybrid database.

In an embodiment, the second management part 202 is also configured to:

Calling the first database business interface at the interface layer of the first database;

Send a preset second database connection interface calling instruction to the first database business interface to convert the currently called first database business interface into the preset second database connection interface.

In one embodiment, the device 20 further includes:

The third management part is configured to uniformly manage all context data generated when accessing the first database and the second database to share all context data;

In one embodiment, the third management part is further configured to:

Based on the preset second database connection interface, send the second database service to the second database to obtain the corresponding second database service processing result;

In one embodiment, the third management part is further configured to:

When it is necessary to access the first database in the first database access environment of the hybrid database, the preset first database business interface is called at the interface layer of the first database;

Based on the preset first database service interface, send the first database service to the first database to obtain the corresponding first database service processing result;

In one embodiment, the first database is a graph database, and the second database is a relational database; the first database access environment is a data query environment using the Gremlin graph query language, and the second database access environment is a data query environment using the JDBC relational query language. In the query environment, the first database business interface is the Gremlin business interface, and the second database connection interface is the JDBC connection interface.

Regarding the hybrid database management device in this embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

The hybrid database management device provided by the embodiment of the present application is used to execute the hybrid database management method provided by the above embodiment. Its implementation method is the same as the principle, and will not be described again.

The embodiment of the present application provides a hybrid database for applying the hybrid database management method provided in the above embodiment.

As shown in Figure 3, it is a schematic structural diagram of a hybrid database provided by an embodiment of the present application. The hybrid database 30 includes: a first database 301, a second database 302, and the hybrid database management device 20 provided in the above embodiment.

Among them, the interface layer of the first database has a preset second database connection interface; the interface layer of the second database has a preset first database connection interface; the hybrid database management adopts the hybrid database management method provided in the above embodiment. The management method manages the first database and the second database.

The hybrid database provided by the embodiment of the present application is used to apply the hybrid database management method provided by the above embodiment. Its implementation method is the same as the principle, and will not be described again.

The embodiment of the present application provides an electronic device for executing the hybrid database management method provided in the above embodiment.

As shown in Figure 4, it is a schematic structural diagram of an electronic device provided by an embodiment of the present application. The electronic device 40 includes: at least one processor 41 and a memory 42 .

The memory stores computer-executed instructions; at least one processor executes the computer-executed instructions stored in the memory, so that at least one processor executes the hybrid database management method provided by the above embodiment.

An electronic device provided by an embodiment of the present application is used to execute the hybrid database management method provided by the above embodiment. Its implementation method is the same as the principle, and will not be described again.

Embodiments of the present application provide a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When the processor executes the computer-executed instructions, the hybrid database management method provided in any of the above embodiments is implemented.

The storage medium containing computer-executable instructions in the embodiment of the present application can be used to store the computer-executable instructions of the hybrid database management method provided in the previous embodiment. The implementation method and principle are the same and will not be described again.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes a number of instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute the methods described in various embodiments of this application. Some steps. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated to different functional modules according to needs, that is, the device The internal structure is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the device described above, reference can be made to the corresponding process in the foregoing method embodiment, which will not be described again here.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or substitutions do not deviate from the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present application. scope.

Industrial applicability

The embodiment of the present application discloses a hybrid database management method, device, hybrid database and electronic device, including: based on the shared connection of the hybrid database server, establishing communication with each database included in the hybrid database to enter the first database access environment or the second database access environment; wherein the hybrid database includes the first database and the second database; when the second database needs to be accessed in the first database access environment of the hybrid database, calling the preset second database connection interface at the interface layer of the first database to connect and access the second database. In this way, by implementing the call of the second database connection interface in the first database access environment, the second database can be quickly switched to access the second database, thereby improving the application efficiency of the hybrid database.

Claims

A hybrid database management approach that includes:

Based on the shared connection of the hybrid database server, establish communication with each database included in the hybrid database to enter the first database access environment or the second database access environment; wherein the hybrid database includes a first database and a second database;

When it is necessary to access the second database in the first database access environment of the hybrid database, the preset second database connection interface is called at the interface layer of the first database to connect and access the second database.
The method according to claim 1, wherein calling the preset second database connection interface at the interface layer of the first database includes:

Call the first database business interface at the interface layer of the first database;

A preset second database connection interface calling instruction is sent to the first database service interface to convert the currently called first database service interface into a preset second database connection interface.
The method of claim 1, further comprising:

Unified management of all context data generated when accessing the first database and the second database to share all context data;

Wherein, the context data includes at least session context data, user security authority context data and database transaction context data.
The method of claim 1, further comprising:

Based on the preset second database connection interface, send a second database service to the second database to obtain the corresponding second database service processing result;

Wherein, the second database service is processed based on the second database data processing engine.
The method of claim 4, further comprising:

When it is necessary to access the first database in the first database access environment of the hybrid database, calling the preset first database business interface in the interface layer of the first database;

Based on the preset first database service interface, send a first database service to the first database to obtain the corresponding first database service processing result;

Wherein, the first database service is processed based on the first database data processing engine.
The method according to claim 2, wherein the first database is a graph database and the second database is a relational database;

The first database access environment is a data query environment using Gremlin graph query language, the second database access environment is a data query environment using JDBC relational query language, the first database business interface is a Gremlin business interface, and the The second database connection interface is JDBC connection interface.
A hybrid database management device, including:

The first management part is configured to establish communication with each database included in the hybrid database based on the shared connection of the hybrid database server to enter the first database access environment or the second database access environment; wherein the hybrid database includes the first database and the second database;

The second management part is configured to call the preset second database connection interface at the interface layer of the first database when it is necessary to access the second database in the first database access environment of the hybrid database to connect and Access the second database.
The device according to claim 7, wherein the second management part is further configured to call a first database business interface at the interface layer of the first database; send a preset value to the first database business interface. The second database connection interface calls instructions to convert the currently called first database business interface into a preset second database connection interface.
The device according to claim 7, wherein the device further comprises:

A third management part configured to uniformly manage all context data generated when accessing the first database and the second database to share all context data;

Wherein, the context data includes at least session context data, user security authority context data and database transaction context data.
The device according to claim 7, wherein the third management part is further configured to send a second database service to the second database based on the preset second database connection interface to obtain the corresponding second database service. Database business processing results;

Wherein, the second database service is processed based on the second database data processing engine.
The device according to claim 10, wherein the third management part is further configured to: when accessing the first database is required in the first database access environment of the hybrid database, the interface of the first database The layer calls the preset first database service interface; based on the preset first database service interface, sends the first database service to the first database to obtain the corresponding first database service processing result;

Wherein, the first database service is processed based on the first database data processing engine.
The device according to claim 8, wherein the first database is a graph database and the second database is a relational database;

The first database access environment is a data query environment using the Gremlin graph query language, the second database access environment is a data query environment using the JDBC relational query language, the first database business interface is a Gremlin business interface, and the second database connection interface is a JDBC connection interface.
A hybrid database, including: a first database, a second database and as claimed in claim 7 The hybrid database management device;

The interface layer of the first database has a preset second database connection interface;

The interface layer of the second database has a preset first database connection interface;

The hybrid database management uses the hybrid database management method according to any one of claims 1 to 6 to manage the first database and the second database.
An electronic device including: at least one processor and memory;

The memory stores computer execution instructions;

The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the method according to any one of claims 1 to 6.
A computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When a processor executes the computer-executable instructions, the method according to any one of claims 1 to 6 is implemented.