WO2020168755A1 - Method and device for controlling database operation, computer apparatus and storage medium - Google Patents

Abstract

A method for controlling a database operation comprises: receiving a database operation request carrying an operation identifier; searching for lock data corresponding to the operation identifier, the lock data comprising operation objects corresponding to the operation identifier and lock types corresponding to the respective operation objects; determining, according to a pre-defined mutually exclusive relationship between lock types, whether there is a conflict between the lock data and lock data in an operation lock record table, the lock data in the operation lock record table comprising lock data corresponding to a currently executing operation; and if there is a conflict between the lock data and the lock data in the operation lock record table, blocking the requested operation; or if there is no conflict between the lock data and the lock data in the operation lock record table, executing the operation, and adding the lock data corresponding to the operation to the operation lock record table.

Description

Database operation control method, device, computer equipment and storage medium

This application claims the priority of the Chinese patent application filed to the Chinese Patent Office on February 20, 2019, with the application number 2019101257260 and the application titled "Database Operation Control Method, Device, Computer Equipment, and Storage Medium". The reference is incorporated in this application.

Technical field

This application relates to a database operation control method, device, computer equipment and storage medium.

Background technique

In database services, customers do many operations on many objects (such as DB instances, users, etc.), and most of the operations are not completed immediately, which takes tens of seconds to several minutes. The operations of different customers on different objects may be related, and some may affect each other, and cannot be executed at the same time. For example, if customer U1 is expanding the storage capacity for library A, when customer U2 initiates the creation of a same-city disaster recovery library for library A, then the latter should not be allowed to execute, otherwise an error will be reported in the middle of the execution, and it will be difficult to continue. Or roll back. The inventor realizes that in order to avoid conflicts between operations, the traditional approach is to hard-code these business rules into the program. But when the volume of database products is large, hard coding simply cannot cope with such a huge business logic.

Summary of the invention

According to various embodiments disclosed in the present application, a database operation control method, device, computer equipment, and storage medium are provided.

A database operation control method includes:

Receiving a database operation request, the request carrying an operation identifier;

Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object;

Determine whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes lock data corresponding to the operation being executed in the state;

If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and

If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table.

A database operation control device includes:

The operation request receiving module is configured to receive a database operation request, and the request carries an operation identifier;

A lock data search module, configured to search lock data corresponding to the operation identifier, the lock data including the operation object corresponding to the operation identifier and the lock type corresponding to each operation object;

The conflict judgment module is used for judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types. The lock data in the operation lock record table includes the status of being executed Operate the corresponding lock data;

If yes, enter the blocking module, otherwise enter the execution module; and

The blocking module is used to block the requested operation; the execution module is used to execute the operation and add lock data corresponding to the operation to the operation lock record table.

A computer device, including a memory and one or more processors, the memory stores computer readable instructions, when the computer readable instructions are executed by the processor, the one or more processors execute The following steps:

Receiving a database operation request, the request carrying an operation identifier;

Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object;

Judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes the lock data corresponding to the operation being executed;

If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and

If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table.

One or more non-volatile computer-readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors perform the following steps:

Receiving a database operation request, the request carrying an operation identifier;

Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object;

Judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes the lock data corresponding to the operation being executed;

If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and

If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table.

The details of one or more embodiments of the application are set forth in the following drawings and description. Other features and advantages of this application will become apparent from the description, drawings and claims.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

Fig. 1 is an application scenario diagram of a database operation control method according to one or more embodiments.

Fig. 2 is a schematic flowchart of a method for controlling database operations according to one or more embodiments.

Fig. 3 is a schematic flowchart of a step of searching lock data corresponding to an operation according to one or more embodiments.

Fig. 4 is a block diagram of a database operation control device according to one or more embodiments.

Figure 5 is a block diagram of a computer device according to one or more embodiments.

detailed description

In order to make the technical solutions and advantages of the present application clearer, the following further describes the present application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the application, but not to limit the application.

The database operation control method provided in this application can be applied to the application environment as shown in FIG. 1. The terminal 102 communicates with the server 104 through the network through the network. The terminal 102 sends a database operation request to the server 104. The server 104 extracts the operation identifier carried in the request, searches for the lock data corresponding to the operation identifier, and determines whether the lock data conflicts with the lock data being executed in the operation lock record table. The conflict judgment result controls whether the currently requested operation is executed. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server 104 may be implemented by an independent server or a server cluster composed of multiple servers.

In one of the embodiments, as shown in FIG. 2, a database operation control method is provided. Taking the method applied to the server in FIG. 1 as an example for description, the method includes the following steps:

Step 202: Receive a database operation request, and the request carries an operation identifier.

Based on the request of the terminal, the server can perform a series of database operations. Take distributed relational database services as an example. Distributed relational database services include many operable entities, such as MyCat entities, MySQL entities, and so on.

The terminal can request the operation of any object in the database, such as requesting to release the MyCat entity and request to restart the MySQL entity.

The requested operation identifier can be the name of the requested operation, such as "release MyCat entity", "restart MySQL entity", or the operation code, such as OTD:DC (meaning "release MyCat entity"), OTY:RS (meaning " Restart the MySQL entity").

Step 204: Search for lock data corresponding to the operation identifier. The lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object.

In one of the embodiments, the lock types include exclusive locks and shared locks.

The operation object corresponding to each operation identifier and the lock type corresponding to each operation object are defined in advance. The lock type corresponding to the operation object can be an exclusive lock or a shared lock. The lock type corresponding to the operation object is defined according to the actual business logic. If in the actual business logic, if an operation object can be used by multiple operation threads at the same time, and multiple operation threads call and execute the operation object at the same time without any failure, add a shared lock for the operation object. Correspondingly, if a certain operation object cannot be used by multiple operation threads at the same time, and multiple operation threads call and execute the operation object at the same time, it will fail, so add an exclusive lock for the operation object.

The lock data corresponding to the operation includes the operation object and the lock type corresponding to each operation object. For example, the lock data corresponding to the operation identifier may be operation object A-exclusive lock, operation object B-shared lock, operation object C exclusive lock, etc.

Step 206: Determine whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types. The lock data in the operation lock record table includes the lock data corresponding to the operation being executed in the status. , Go to step 208, otherwise, go to step 210.

Step 208: Block the requested operation.

Step 210: Perform an operation, and add lock data corresponding to the operation to the operation lock record table.

In one of the embodiments, determining whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types includes: if the lock type of the operation object in the current request is a shared lock, and When the lock type of the same operation object in the operation lock record table is an exclusive lock, it is determined that the lock data conflicts;

Or when the lock type of the operation object in the current request is an exclusive lock, and the same operation object in the operation lock record table is an exclusive lock or a shared lock, it is determined that the lock data conflicts.

The operation lock record table records the lock data corresponding to the operation currently being performed, as shown in Table 1 below.

Table 1

The operation being performed in Table 1 is "release MyCat entity". The operation objects corresponding to this operation include ccm_mycat_entity=101, ccm_mysql_entity=251, ccm_mysql_entity=252, ccm_mysql_entity=253, ccm_mysql_entity=254, and the lock types corresponding to these operation objects are all X (exclusive lock). In other words, the operation lock record table records the lock information of all operation objects currently being executed.

After the server receives the new operation request, it extracts the lock data corresponding to the new operation request, and judges whether the lock data corresponding to the new operation request conflicts with the lock data corresponding to the operation being performed in the operation lock data table, and if so, it blocks New operation request. Exclusive locks conflict with shared locks, exclusive locks conflict with exclusive locks, and shared locks do not conflict with shared locks. Corresponding to the same operation object, when the operation object involved in the new operation request is a shared lock and the same operation object in the operation lock record table is also a shared lock, or the operation object in the new operation request is a shared lock or an exclusive lock, the operation lock record If there is no lock record for the same operation object in the table (that is, the operation object is not locked in the operation lock record), the lock data of the operation object does not conflict.

If any operation object in the currently requested operation conflicts with the operation lock record table, the operation conflicts with the operation lock record table. As long as all operation objects of the requested operation do not conflict with the operation lock record table, the operation does not conflict with the operation lock record table.

For example, the operation lock record table is shown in Table 1. The currently requested operation is "Restart MySQL", the operation object corresponding to "Restart MySQL" is found to be ccm_mysql_entity=251, and the lock type corresponding to the operation object is an exclusive lock.

Query the operation lock record table and find that there is an operation record that is executing object name=ccm_mysql_entity, object id=251, and the lock type of the operation object in the operation record table is an exclusive lock. Therefore, the operation object and operation lock of "restart MySQL entity" The lock data in the record conflicts, so the server blocks the "restart MySQL entity" operation.

Further, the server monitors the operation being performed, and when the operation is completed, it automatically deletes the corresponding operation lock record from the operation lock record table. If the execution of "Release MyCat Entity" is completed, the operation time in Table 1 is "2018/10/23 14:12" and the operation type is "Release MyCat Entity" operation lock data is automatically deleted.

In one of the embodiments, after the server blocks the mutually exclusive request, it adds a label to the blocked operation. The label includes abandonment and wait. If the waiting label is added to the blocked operation, the target lock record that is mutually exclusive with the operation in the operation lock record is monitored. When the target lock record is deleted from the operation lock record, the blocked operation is automatically executed. If the blocked operation adds a discarded label, the blocked operation will not be executed again.

For another example, the currently requested operation is "Restart MySQL", the operation object corresponding to "Restart MySQL" is found to be ccm_mysql_entity=257, and the lock type corresponding to this operation object is an exclusive lock. If there is no operation record of the operation object ccm_mysql_entity=257 in the operation lock record table, the currently requested operation "restart MySQL" does not conflict with the operation lock record table, so the operation is executed and the lock data corresponding to the operation is added to the operation lock recording sheet. As shown in table 2:

Table 2

In this embodiment, the operation object corresponding to the operation is defined in advance, the lock type is defined for the operation object, and whether the currently requested operation is executed is determined by whether there is a lock conflict between the currently requested operation and the currently executed operation. In this embodiment, there is no need to write a large number of logically complex hard codes to achieve mutual exclusion of operations. The mutual exclusion judgment between various operations can be realized only by pre-defining the lock data corresponding to the operation and the mutual exclusion rules between the lock data. .

In one of the embodiments, as shown in FIG. 3, step 204, searching for lock data corresponding to the operation identifier, includes:

Step 302: Obtain an operation definition corresponding to the operation identifier, where the operation definition includes a query statement.

Predefine standard operations, including standard operation names, operation codes, input parameter types, query statements, and lock types. as shown in Table 3:

table 3

Two standard operations are defined in Table 3. Among them, "release MyCat entity" includes two definition lines. The difference is that the query statements are different. The meaning of the query statement in the first definition line is: find id_mycat_entity, and find id_mysql_entity associated with id_mycat_entity from ccm_mycat_member. Simply put, it is to find the mysql entity associated with the MyCat entity. The query statement in the second definition line is: query the id_mycat_entity of the mycat entity itself.

Step 304: Search for an operation object corresponding to the operation identifier according to the query statement. The operation object includes the operation itself and configuration items associated with the operation.

If the terminal requests "Release MyCat Entity", the server searches for the operation definition corresponding to "Release MyCat Entity", such as the first row and the second row in Table 3. Then get the query statement in the definition, and find the operation object associated with "release MyCat entity" from the configuration management system through the first query statement. The configuration management database records the information of related configuration items. Let's take the DRDS distributed relational database service (Distributed Relational Database Service) as an example. CCM_MYCAT_ENTITY is the table corresponding to MyCat entity, MyCat entity is a configuration item, it is a distributed database middleware. One MyCat entity corresponds to multiple MySQL entities (that is, another configuration item), and the relationship between the MyCat entity and the MySQL entity is recorded in ccm_mycat_member. Therefore, first obtain the identity of the MyCat entity (101), and then look up the MySQL entity associated with the MyCat entity from the mycat_member association table.

Table 4

id_mycat_menber Id_mycat_entity Id_mysql_entity … 10 101 251 …

11 101 252 … 12 101 253 … 13 101 254 …

As shown in Table 4, in the mycat_menber association table, four id_mysql_entities associated with id_mycat_entity(101) are queried: 251, 252, 253, and 254. Therefore, the operation objects associated with "release MyCat entity" include ccm_mysql_entity=251, ccm_mysql_entity=252, ccm_mysql_entity=253, ccm_mysql_entity=254, where ccm_mysql_entity is the object name, which is determined according to the locked object in the definition.

Through the second line of query statement, select$1, the query is id_mycat_entity itself, and the determined operation object is ccm_mycat_entity=101. The same ccm_mycat_entity is determined based on the locked object in the definition, and 101 is found by the query statement.

Further, according to the actual business logic, there may also be configuration items of other dimensions associated with the "release MyCat entity" operation. If there are, there are third and fourth rows of definitions when defining the release of the MyCat entity operation. Etc., each row defines configuration items corresponding to a dimension, and configuration items of the same dimension have the same lock type. For example, there are 4 associated id_mysql_entity in the first row. These four configuration items belong to the same latitude, and the corresponding lock type is also The same, as shown in Table 3, is an exclusive lock. Configuration items in other dimensions are configured as exclusive locks or shared locks according to specific business logic.

Step 306: Obtain the lock type corresponding to each operation object from the operation definition.

Step 308: Generate lock data corresponding to the operation identifier according to the operation object and the lock type corresponding to the operation object.

The query statement is used to query the multi-dimensional configuration items associated with the current operation and the operation itself, and these configuration items and the operation itself are the operation objects corresponding to the operation. Obtain the lock type corresponding to each operation object from the operation definition.

The operation object corresponding to the operation identifier and the lock type corresponding to each operation object constitute the lock data of the current operation.

In this embodiment, the configuration management library is constructed through the influence relationship between operations, the standard operations are defined according to the association relationship between the configurations in the configuration management library, and the associated configuration items and configuration items of the identification operations are searched through the query statements in the standard operation definitions. Lock type. Quickly querying the configuration items that have an influence relationship with the current requested operation is the main prerequisite for judging the operation conflict. In this embodiment, all the configuration items that have an influence relationship corresponding to the operation can be predefined, and these configuration items can be quickly obtained based on the query statement. Configuration item. Comprehensive consideration of all associated configuration items (including the operation itself) can make the operation conflict judgment more accurate, and effectively reduce the probability of operation execution failure.

In one of the embodiments, the operation object corresponding to the currently requested operation includes the operation itself and the multi-dimensional configuration items associated with the operation. In step 206, it is determined whether the lock data conflicts with the lock data in the operation lock record table, specifically:

Judge one by one whether the operation object corresponding to the currently requested operation is locked in the operation lock record table.

The meaning of the operation lock record table to lock the operation object is that there is a lock record for the operation object in the operation record table. As shown in Table 1, the operation lock record table locks 5 operation objects, which are divided into It is the operation object: ccm_mycat_entity=101, ccm_mysql_entity=251, ccm_mysql_entity=252, ccm_mysql_entity=253, ccm_mysql_entity=254.

In this embodiment, the operation object corresponding to the currently requested operation includes multiple operation objects, which are the operation itself and associated multi-dimensional configuration items. For example, the operation itself, the configuration item of the first dimension, and the configuration item of the second dimension are included, assuming that each dimension includes only one configuration item. Of course, each dimension configuration item may also include multiple configuration items.

The server determines one by one whether the operation itself is locked in the operation lock record table, whether the first dimension configuration item is locked, whether the second dimension configuration item is locked, if the operation lock record table is for these operation objects Locking means that the lock data of the current operation does not conflict with the lock data in the operation lock record table, and the currently requested operation can be directly executed, and the lock data corresponding to the currently requested operation is added to the operation lock record table.

If there is a lock record for the operation itself in the operation lock record table, obtain the lock type of the operation itself (one of the operation objects) in the operation lock record, and obtain the lock type of the operation object in the lock data of the current operation, mainly when When both lock types are shared locks, the lock data of the operation object does not conflict. Or only obtain the lock type of the locked operation object in the operation lock record. If the lock type is an exclusive lock, the lock data of the operation object conflicts. Among all operation objects corresponding to the operation, if the lock data of any operation object conflicts with the lock data in the operation lock record table, the lock data of the operation conflicts with the lock data in the operation lock record table. Correspondingly, only The lock data corresponding to all operation objects does not conflict with the lock data in the operation lock record table, and the lock data of the operation does not conflict with the lock data in the operation lock record table.

Further, during conflict judgment, if there is a conflict, a lock record that conflicts with the lock type of the currently operated operation object is obtained from the operation lock record table.

For example, the operation lock record table is shown in Table 1. The currently requested operation is "Restart MySQL", the operation object corresponding to "Restart MySQL" is found to be ccm_mysql_entity=251, and the lock type corresponding to the operation object is an exclusive lock.

Query the operation lock record table, and found that there is an operation record of the object name being executed=ccm_mysql_entity and object id=251. This operation record conflicts with the operation object ccm_mysql_entity=251 of the current requested operation, so the lock type of the operation object in the operation record table It is an exclusive lock. Therefore, the configuration item of "Restart MySQL entity" conflicts with the lock data in the operation lock record, and the conflict to be acquired by "2018/10/23 14:12 release MyCat entity ccm_mysql_entity 251 X in execution" Target lock record.

A blocking reminder template can be defined in advance. When a blocking reminder is generated, the data in the target lock record is filled into the blocking reminder template to generate a blocking reminder.

It should be understood that, although the various steps in the flowchart of FIGS. 2-3 are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless specifically stated in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least some of the steps in Figure 2-3 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. These sub-steps or stages The execution order of is not necessarily performed sequentially, but may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

In one of the embodiments, as shown in FIG. 4, a database operation control device is provided, including: an operation request receiving module 402, a lock data search module 404, a conflict judgment module 406, a blocking module 408, and an execution module 410, wherein :

The operation request receiving module 402 is configured to receive a database operation request, and the request carries an operation identifier.

The lock data search module 404 is used to search for lock data corresponding to the operation identifier. The lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object.

The conflict judgment module 406 is used to judge whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types. The lock data in the operation lock record table includes the status corresponding to the operation being executed Lock data.

If yes, enter the blocking module 408, otherwise enter the execution module 410; the blocking module 408 is used to block the requested operation; the execution module 410 is used to perform the operation and add the lock data corresponding to the operation to the operation lock record table.

In one of the embodiments, the lock types include exclusive locks and shared locks; the conflict judgment module 404 is also used to if the lock type of the operation object in the current request is a shared lock, and the lock type of the same operation object in the operation lock record table is When an exclusive lock is used, it is determined that the lock data conflicts; or the lock type of the operation object in the current request is an exclusive lock, and when the same operation object in the operation lock record table is an exclusive lock or a shared lock, it is determined that the lock data conflicts.

In one of the embodiments, the lock data search module 404 is also used to obtain the operation definition corresponding to the operation identification. The operation definition includes a query statement; according to the query statement, the operation object corresponding to the operation identification is found. The operation object includes the operation itself and the operation Associated configuration items; obtain the lock type corresponding to each operation object from the operation definition; and generate lock data corresponding to the operation identifier according to the operation object and the lock type corresponding to the operation object.

In one of the embodiments, the conflict judgment module 404 is also used to judge whether the operation object is locked in the operation lock record table; if so, it is judged whether the lock record in the operation lock record table matches the lock type of the operation object in the operation definition. Conflict; if the lock type of any operation object conflicts with the lock record, the operation is blocked; and if the lock type of all operation objects does not conflict with the lock record, the operation is executed.

In one of the embodiments, the database operation control device further includes a blocking reminder module for obtaining conflicting target lock records from the operation lock records; and generating a blocking reminder according to the target lock record, and sending the blocking reminder to the operation request terminal.

In one of the embodiments, the database operation control device further includes an operation lock record table update module for monitoring the operation being performed; and when the operation is completed, the lock data corresponding to the operation is deleted from the operation lock record table.

In one of the embodiments, the operation lock record table update module is also used to mark the blocked operation according to the tag; when the tag is a waiting tag, monitor the target lock record in the operation lock record that is mutually exclusive with the operation; and when the target lock After the record is deleted from the operation lock record, the operation of waiting for label marking is performed.

For the specific limitation of the database operation control device, please refer to the above limitation on the database operation control method, which will not be repeated here. Each module in the aforementioned database operation control device can be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in the form of hardware or independent of the processor in the computer equipment, or may be stored in the memory of the computer equipment in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. 5. The computer equipment includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium. The database of the computer equipment is used to store lock data. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer readable instruction is executed by the processor to realize a database operation control method.

Those skilled in the art can understand that the structure shown in FIG. 5 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.

A computer device includes a memory and one or more processors. The memory stores computer readable instructions. When the computer readable instructions are executed by the processor, the one or more processors execute the method in the foregoing method embodiment. step.

One or more non-volatile computer-readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, one or more processors execute A step of.

A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing relevant hardware through computer-readable instructions, which can be stored in a non-volatile computer. In a readable storage medium, when the computer-readable instructions are executed, they may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database, or other media used in the embodiments provided in this application may include non-volatile and/or volatile memory. Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not a limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, they should It is considered as the range described in this specification.

The above-mentioned embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the scope of the invention patent. It should be pointed out that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can be made, and these all fall within the protection scope of this application. Therefore, the scope of protection of the patent of this application shall be subject to the appended claims.

Claims (20)

A database operation control method, including: Receiving a database operation request, the request carrying an operation identifier; Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object; Judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes the lock data corresponding to the operation being executed; If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table. The method according to claim 1, wherein the lock types include exclusive locks and shared locks; The judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types includes: If the lock type of the operation object in the current request is a shared lock, and the lock type of the same operation object in the operation lock record table is an exclusive lock, determining that the lock data conflicts; and Or when the lock type of the operation object in the current request is an exclusive lock, and the same operation object in the operation lock record table is an exclusive lock or a shared lock, it is determined that the lock data conflicts. The method according to claim 1, wherein the searching for lock data corresponding to the operation identifier comprises: Acquiring an operation definition corresponding to the operation identifier, where the operation definition includes a query statement; Searching for an operation object corresponding to the operation identifier according to the query sentence, the operation object including the operation itself and configuration items associated with the operation; Obtain the lock type corresponding to each operation object from the operation definition; and According to the operation object and the lock type corresponding to the operation object, lock data corresponding to the operation identifier is generated. The method according to claim 3, wherein the determining whether the lock data conflicts with the lock data in the operation lock record table comprises: Determine whether the operation object is locked in the operation lock record table; If yes, determine whether the lock record in the operation lock record table conflicts with the lock type of the operation object in the operation definition; If the lock type of any of the operation objects conflicts with the lock record, the operation is blocked; and If the lock types of all the operation objects do not conflict with the lock record, the operation is performed. The method according to any one of claims 1 to 4, characterized in that, after the operation of the blocking request, the method further comprises: Obtain the conflicting target lock record from the operation lock record; and A blocking reminder is generated according to the target lock record, and the blocking reminder is sent to the operation request terminal. The method according to any one of claims 1 to 4, wherein after the execution of the operation, the lock data corresponding to the operation is added to the operation lock record table, the method further comprises: Monitor the operation being performed; and When the execution of the operation is completed, the lock data corresponding to the operation is deleted from the operation lock record table. The method according to any one of claims 1 to 4, characterized in that, after the operation of the blocking request, the method further comprises: Mark the blocked operation according to the label; When the tag is a waiting tag, monitor the target lock record that is mutually exclusive with the operation in the operation lock record; and After the target lock record is deleted from the operation lock record, the operation of waiting for the tag mark is performed. A database operation control device, including: The operation request receiving module is configured to receive a database operation request, and the request carries an operation identifier; A lock data search module, configured to search lock data corresponding to the operation identifier, the lock data including the operation object corresponding to the operation identifier and the lock type corresponding to each operation object; The conflict judgment module is used for judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types. The lock data in the operation lock record table includes the status of being executed Operate the corresponding lock data; If yes, enter the blocking module, otherwise enter the execution module; and The blocking module is used to block the requested operation; the execution module is used to execute the operation and add lock data corresponding to the operation to the operation lock record table. The device according to claim 8, wherein the lock type includes an exclusive lock and a shared lock; the conflict judgment module is further configured to: if the lock type of the operation object in the current request is a shared lock, and When the lock type of the same operation object in the operation lock record table is an exclusive lock, it is determined that the lock data conflicts; or the lock type of the operation object in the current request is an exclusive lock, and the same operation lock record table is the same When the operation object is an exclusive lock or a shared lock, it is determined that the lock data conflicts. A computer device includes a memory and one or more processors, the memory stores at least one computer readable instruction, and the computer readable instruction is loaded by the processor and executes the following steps: Receiving a database operation request, the request carrying an operation identifier; Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object; Judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes the lock data corresponding to the operation being executed; If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table. The computer device according to claim 10, wherein the lock types include exclusive locks and shared locks; when the processor executes computer-readable instructions, the following steps are also executed: if the operation object in the current request is When the lock type is a shared lock, and the lock type of the same operation object in the operation lock record table is an exclusive lock, it is determined that the lock data conflicts; or the lock type of the operation object in the current request is an exclusive lock When the same operation object in the operation lock record table is an exclusive lock or a shared lock, it is determined that the lock data conflicts. The computer device according to claim 10, wherein the processor further executes the following steps when executing computer-readable instructions: acquiring an operation definition corresponding to the operation identifier, the operation definition including a query sentence; The query sentence searches for the operation object corresponding to the operation identifier, the operation object includes the operation itself and the configuration items associated with the operation; obtains the lock type corresponding to each operation object from the operation definition; and According to the operation object and the lock type corresponding to the operation object, lock data corresponding to the operation identifier is generated. The computer device according to claim 12, wherein the processor further executes the following steps when executing computer-readable instructions: determining whether the operation object is locked in the operation lock record table; if so, determining the operation Whether the lock record in the lock record table conflicts with the lock type of the operation object in the operation definition; if the lock type of any of the operation objects conflicts with the lock record, the operation is blocked; and If the lock types of all the operation objects do not conflict with the lock record, the operation is performed. The computer device according to any one of claims 10-13, wherein the processor further executes the following steps when executing the computer-readable instructions: obtaining conflicting target lock records from the operation lock records; and A blocking reminder is generated according to the target lock record, and the blocking reminder is sent to the operation request terminal. The computer device according to any one of claims 10-13, wherein the processor further executes the following steps when executing computer-readable instructions: monitoring the operation being performed; and when the operation is completed , Delete the lock data corresponding to the operation from the operation lock record table. A non-volatile computer-readable storage medium in which at least one computer-readable instruction is stored, and the computer-readable instruction is loaded by a processor and executes the following steps: Receiving a database operation request, the request carrying an operation identifier; Searching lock data corresponding to the operation identifier, where the lock data includes the operation object corresponding to the operation identifier and the lock type corresponding to each operation object; Judging whether the lock data conflicts with the lock data in the operation lock record table according to the pre-defined mutual exclusion relationship of lock types, and the lock data in the operation lock record table includes the lock data corresponding to the operation being executed; If the lock data conflicts with the lock data in the operation lock record table, the requested operation is blocked; and If the lock data does not conflict with the lock data in the operation lock record table, the operation is executed, and the lock data corresponding to the operation is added to the operation lock record table. The storage medium according to claim 16, wherein the lock types include exclusive locks and shared locks; when the computer-readable instructions are executed by the processor, the following steps are also executed: if the current request is When the lock type of the operation object is a shared lock, and the lock type of the same operation object in the operation lock record table is an exclusive lock, it is determined that the lock data conflicts; or the lock type of the operation object in the current request It is an exclusive lock, and when the same operation object in the operation lock record table is an exclusive lock or a shared lock, it is determined that the lock data conflicts. The storage medium according to claim 16, wherein when the computer-readable instructions are executed by the processor, the following steps are further performed: obtaining an operation definition corresponding to the operation identifier, the operation definition including a query statement Find the operation object corresponding to the operation identifier according to the query sentence, the operation object includes the operation itself and the configuration items associated with the operation; obtain the lock corresponding to each operation object from the operation definition Type; and according to the operation object and the lock type corresponding to the operation object, generating lock data corresponding to the operation identifier. 18. The storage medium according to claim 18, wherein when the computer-readable instructions are executed by the processor, the following steps are further executed: determining whether the operation object is locked in the operation lock record table; if so, determining Whether the lock record in the operation lock record table conflicts with the lock type of the operation object in the operation definition; if the lock type of any of the operation objects conflicts with the lock record, block the Operation; and if the lock types of all the operation objects do not conflict with the lock record, the operation is performed. The storage medium according to any one of claims 16-19, wherein when the computer-readable instruction is executed by the processor, the following step is further executed: obtaining a conflicting target lock from the operation lock record Record; and generate a block reminder according to the target lock record, and send the block reminder to the operation request terminal.

Images