WO2021103969A1 - 一种触发器实现的方法和装置 - Google Patents

一种触发器实现的方法和装置 Download PDF

Info

Publication number
WO2021103969A1
WO2021103969A1 PCT/CN2020/126580 CN2020126580W WO2021103969A1 WO 2021103969 A1 WO2021103969 A1 WO 2021103969A1 CN 2020126580 W CN2020126580 W CN 2020126580W WO 2021103969 A1 WO2021103969 A1 WO 2021103969A1
Authority
WO
WIPO (PCT)
Prior art keywords
trigger
request
statement
write
parameter value
Prior art date
Application number
PCT/CN2020/126580
Other languages
English (en)
French (fr)
Inventor
王海军
丁岩
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20891959.7A priority Critical patent/EP4050495A4/en
Publication of WO2021103969A1 publication Critical patent/WO2021103969A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24564—Applying rules; Deductive queries
    • G06F16/24565—Triggers; Constraints
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2453—Query optimisation
    • G06F16/24534—Query rewriting; Transformation
    • G06F16/24542—Plan optimisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • This application relates to the field of database technology, and in particular to a method and device for trigger realization.
  • Trigger is a method provided by the database to programmers and analysts to ensure data integrity. It is a special stored procedure related to table events. Its execution is not called by the program, but triggered by events, such as when When an operation is performed on a table, it will be activated for execution.
  • the embodiment of the present application provides a trigger implementation method, including: determining a write statement request execution plan tree and a trigger execution plan tree corresponding to the write statement request according to the type of the write statement request; combining the write statement request execution plan tree and The trigger executes the plan tree and gets the write request to trigger the plan tree; executes the write request to trigger the plan tree.
  • the embodiment of the present application provides a trigger implementation device, including: a sub-execution plan tree acquisition module, used to determine the execution plan tree of the write statement request and the trigger execution plan tree corresponding to the write statement request according to the type of the write statement request ;
  • the write request trigger plan tree acquisition module is used to merge the write statement request execution plan tree and the trigger execution plan tree to obtain the write request trigger plan tree;
  • the trigger plan tree execution module is used to execute the write request trigger plan tree.
  • the embodiment of the present application provides a trigger-implemented device, including a memory and a processor, the memory stores a program, and when the program is read and executed by the processor, the trigger-implementation method described above is implemented.
  • the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the aforementioned trigger The method implemented by the device.
  • FIG. 1 is a schematic flowchart of a method for implementing a trigger provided by an embodiment of the present application
  • FIG. 2 is a sequence diagram of creating a trigger interaction provided by an embodiment of the present application
  • FIG. 3 is an interactive sequence diagram of a trigger to trigger an execution statement request according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a device structure implemented by a trigger provided in an embodiment of the present application.
  • Fig. 5 is a schematic diagram of a device for implementing a trigger provided in an embodiment of the present application.
  • FIG. 6 is a block diagram of a storage medium provided by an embodiment of the application.
  • a schematic flow diagram of a trigger implementation method provided by the present application can be applied to the situation where a statement request is triggered by a trigger.
  • the method can be executed by the trigger-implemented device provided in this application, and the trigger-implemented device is implemented by software and/or hardware and integrated on a device.
  • a schematic flow diagram of a trigger implementation method provided by an embodiment of the present application, the method may include:
  • Step 11 Determine the execution plan tree of the write statement request and the trigger execution plan tree corresponding to the write statement request according to the type of the write statement request.
  • determining the execution plan tree of the write statement request and the trigger execution plan tree corresponding to the write statement request according to the type of the write statement request may include: obtaining new parameter values and old parameter values according to the type of the write statement request; The new parameter value, the old parameter value and the metadata corresponding to the trigger obtain the trigger execution plan tree; the write statement request execution plan tree is directly obtained according to the type of the write statement request.
  • the distributed database includes a computing node and a storage node, where the computing node and the storage node perform signaling interaction.
  • the execution plan tree of the statement writing request and the trigger execution plan tree corresponding to the statement writing request may also include: according to the creation request sent by the client, through the computing node and the storage node Create a trigger; save the metadata corresponding to the trigger on the computing node.
  • the types of write statement requests include a first type of write statement request and a second type of write statement request, where the first type of write statement request includes an insert statement, and the second type of write statement request includes an update (update). ) Statement, delete statement or insert...select statement.
  • the new parameter value and the old parameter value are obtained according to the type of the write statement request, including: when it is determined that the type of the write statement request includes an insert statement, the parameter information contained in the insert statement is directly obtained, and the parameter information As the old parameter value; set the new parameter value to be the same as the old parameter value.
  • obtaining the new parameter value and the old parameter value according to the type of the write statement request may include: when it is determined that the type of the write statement request includes the second type of write statement request, sending a data acquisition request to the storage node, and Receive the parameter information returned by the storage node according to the data acquisition request; acquire the new parameter value and the old parameter value according to the parameter information.
  • obtaining the new parameter value and the old parameter value according to the parameter information may include: when it is determined that the type of the write statement request includes an update statement, the parameter information is used as the old parameter value; and the new parameter value is obtained according to the update statement and the old parameter value.
  • the parameter value may include: when it is determined that the type of the write statement request includes an update statement, the parameter information is used as the old parameter value; and the new parameter value is obtained according to the update statement and the old parameter value.
  • obtaining the new parameter value and the old parameter value according to the parameter information may include: when it is determined that the type of the write statement request includes a delete statement or an insert...select statement, the parameter information is used as the old parameter value; The parameter value is the same as the old parameter value.
  • creating a trigger through the computing node and the storage node may include: receiving a creation request sent by the client, where the creation request contains the name of the trigger to be created and the trigger logic ; Determine whether there is a trigger through the computing node, if it exists, it will directly return the trigger existence instruction, otherwise, create a trigger according to the creation request.
  • creating a trigger based on the creation request may include: judging whether the trigger can be pushed down according to the creation request, and if so, sending a push creation request to the storage node through the computing node, and the storage node creates the trigger according to the push creation request And return the metadata corresponding to the trigger to the computing node for storage; otherwise, the computing node directly creates the trigger according to the creation request, and saves the metadata corresponding to the trigger.
  • Step 12 Combine the write statement request execution plan tree and the trigger execution plan tree to obtain the write request trigger plan tree.
  • the obtained statement request execution plan tree and the obtained trigger execution plan tree may be merged, that is, the processing logic contained in the trigger itself is added to the statement writing request itself.
  • the write request triggers the plan tree.
  • the trigger execution plan tree can contain the trigger time, such as before/after (before/after); it can contain monitoring events, such as insert/update/delete; it can contain trigger events, such as insert/update/delete , It may also include a monitoring location, such as a table, etc.
  • this embodiment is only an example for description, and does not limit the specific content of the information contained in the trigger.
  • Step 13 execute the write request to trigger the plan tree.
  • the distributed database can execute the write statement request sent by the client by executing the processing logic contained in the write request trigger plan tree. So as to realize the application of the trigger in the distributed database.
  • the trigger event contained in the trigger is update
  • the trigger time is after
  • the monitoring event is update
  • the monitoring location is table1
  • the write statement request includes table1 and update
  • the update event is determined to be executed
  • the execution is performed according to
  • the specified table1 obtains data from the distributed database and performs corresponding operations.
  • the execution logic of the trigger when executing a write statement request, can be added to the execution logic of the original written statement request, and the original written statement request can be executed through the newly formed execution plan.
  • the application of triggers is realized on the basis of the distributed database, the functional characteristics of the distributed database are enhanced, and the user experience effect is improved.
  • Client means client
  • Proxy means computing node
  • DB means storage node
  • computing node and storage node form a distributed database
  • the distributed database can be based on computing node and storage node.
  • the client's creation request creates a trigger.
  • the distributed database in this embodiment may also include other types of nodes, such as a management node.
  • the computing node mainly refers to the cache when storing the metadata corresponding to the trigger, and the management node is used to implement
  • the management node may also have other applications. Since other applications of the management node are not the focus of this application, they will not be described in detail in this embodiment.
  • the Proxy receives the creation request sent by the Client.
  • the creation request contains the name of the trigger to be created and the trigger logic.
  • the creation request also contains the attribute information of the trigger to be created.
  • the attribute information may include push information or non-squeeze information. This embodiment This is only an example for illustration, and other types of attribute information are also within the protection scope of this application, and will not be repeated in the implementation of this application.
  • the computing node Proxy queries the table information in the distributed database according to the trigger name to determine whether there is a trigger with the same name. If it exists, execute 103; otherwise, execute 104.
  • the Proxy returns a creation request response to the Client, and the creation request response contains the indication information that the trigger with the same name exists.
  • the client When the client confirms that there is no trigger with the same name after query, it will create a trigger according to the creation request.
  • it is judged whether the trigger can be pressed down according to the attribute information contained in the creation request. If it can be pressed down, execute 105; otherwise, execute 107.
  • the computing node Proxy sends a push creation request to the storage node DB, and the storage node DB creates a trigger according to the push creation request, and executes 106 when the creation is completed.
  • the DB will feedback the creation request reply to the Proxy when the trigger creation is completed, and feed back the metadata corresponding to the trigger to the Proxy for storage.
  • the Proxy directly creates a trigger according to the creation request and saves the metadata corresponding to the trigger.
  • the main body that executes the creation of the trigger in the distributed database is different. If it is determined that the depression can be executed, the creation is executed
  • the execution subject of the action is DB. In the case where it is determined that it is not possible to perform the creation action, the execution subject is the Proxy, but regardless of whether the execution subject of the creation action is DB or Proxy, the metadata corresponding to the created trigger will be Save in Proxy.
  • the Proxy returns a creation request response to the Client, and the creation request response contains an indication that the trigger has been created.
  • the Proxy receives the statement request sent by the Client.
  • the type of the write statement request sent by the client Client to the computing node Proxy includes the first type of write statement request and the second type of write statement request, where the first type of write statement request includes an insert statement, and the second type of statement write request includes In the update statement, delete statement, or insert...select statement, in Figure 3, for step 201, the letters Insert are used to indicate the two types of write statement requests, insert and insert...select.
  • write statement request in the embodiment of the present application also includes the table name of the write table, that is, which table in the distributed database the write statement needs to operate on.
  • Proxy will query the saved metadata according to the write table name contained in the write statement request to determine whether there is a corresponding trigger, if it does not exist, execute 203, if it exists, execute 204
  • the Proxy determines that the trigger does not exist, it will only generate a write statement request execution plan tree based on the write statement request. After the write statement request is executed according to the write statement request execution plan tree, it will feed back the write statement to the writing client Client.
  • the request for reply is not the focus of this application if the trigger does not exist, so it will not be repeated in this embodiment.
  • the Proxy determines that the trigger exists, it extracts the previously saved trigger metadata, and the metadata contains the execution logic set for the trigger.
  • the trigger execution plan tree needs to be constructed when it is determined that there is a trigger, and when the trigger execution plan tree is constructed, the new parameter value and the old parameter value are obtained according to the type of the write statement request; according to the new The parameter value, the old parameter value and the metadata corresponding to the trigger obtain the trigger execution plan tree.
  • Proxy For the acquisition of new parameter values and old parameter values, Proxy according to the second type of write statement request including update statement, delete statement or insert...select statement, it needs to issue a select...for update request to the DB to obtain relevant parameter information , And determine the new parameter value and the old parameter value from the relevant parameter information by executing 206 to 208, and the Proxy can directly execute 209 to obtain the insert statement according to the first type of write statement request, without sending a request to the DB to obtain the parameter information.
  • the DB After the DB obtains the request information sent by the Proxy, it will feed back to the Proxy the relevant parameter information that needs to be obtained in the request information according to the request.
  • the parameter information is used as the old parameter value, and the new parameter value is set to be the same as the old parameter value.
  • the parameter information contained in the insert statement is directly obtained, and the parameter information is used as the old parameter value.
  • the new parameter value and the old parameter value can be added to the trigger metadata to obtain a trigger execution plan tree containing trigger processing logic.
  • the Proxy generates a write statement request execution plan tree based on the write statement request, and the write statement request execution plan tree contains the processing logic contained in the original write statement request.
  • the trigger execution plan tree and the write statement request execution plan tree are combined, that is, the processing logic contained in the trigger is added to the processing logic contained in the original written statement request, so as to realize the trigger in the distributed database.
  • the plan tree is triggered to send the write statement request to the DB.
  • the Proxy will send the write statement request to the DB according to the new processing logic contained in the request trigger plan tree, and the DB will execute it.
  • the DB After processing the write statement request, the DB will feed back the processing result to the Proxy.
  • the Proxy sends the processing result fed back by the DB to the Client to reply to the request for writing sentences sent by the Client.
  • FIG. 4 shows a schematic diagram of the device structure implemented by a trigger in an embodiment of the present application.
  • the device includes: a sub-execution plan tree acquisition module 41, configured to determine the execution plan tree of the write statement request according to the type of the write statement request And the trigger execution plan tree corresponding to the write statement request; the write request triggers the plan tree acquisition module 42 for combining the write statement request execution plan tree and the trigger execution plan tree to obtain the write request trigger plan tree; the trigger plan tree execution module 43, used to execute the write request to trigger the plan tree.
  • the trigger-implemented device provided in this embodiment is used to implement the trigger-implementation method of the present application.
  • the implementation principle and technical effect of the trigger-implemented device provided in this embodiment are similar to the trigger-implementation method of the present application.
  • the trigger-implemented device disclosed in the embodiment of the application can add the execution logic of the trigger to the execution logic of the original written statement request when executing the write statement request, and execute the original written statement request through the newly composed execution plan.
  • the application of triggers is realized on the basis of the distributed database, the functional characteristics of the distributed database are enhanced, and the user experience effect is improved.
  • the sub-execution plan tree obtaining module is specifically used to: obtain the new parameter value and the old parameter value according to the type of the write statement request; obtain the trigger execution according to the new parameter value, the old parameter value and the metadata corresponding to the trigger Plan tree:
  • the execution plan tree of the write statement request is directly obtained according to the type of the write statement request.
  • the distributed database includes a computing node and a storage node, where the computing node and the storage node perform signaling interaction.
  • a trigger creation module which is used to: create a trigger through the computing node and the storage node according to the creation request sent by the client; and save the metadata corresponding to the trigger on the computing node.
  • the types of write statement requests include a first type of write statement request and a second type of write statement request, where the first type of write statement request includes an insert statement, and the second type of write statement request includes an update statement, a delete statement, or insert...select statement.
  • the sub-execution plan tree obtaining module obtains the new parameter value and the old parameter value according to the type of the write statement request, it is specifically used for: when it is determined that the type of the write statement request includes an insert statement, the insert statement is directly obtained The parameter information contained in the parameter information is used as the old parameter value; the new parameter value is set to be the same as the old parameter value.
  • the sub-execution plan tree obtaining module obtains the new parameter value and the old parameter value according to the type of the write statement request, it is specifically used to: when it is determined that the type of the write statement request includes the second type of write statement request, then Send a data acquisition request to the storage node, and receive the parameter information returned by the storage node according to the data acquisition request; acquire the new parameter value and the old parameter value according to the parameter information.
  • the sub-execution plan tree obtaining module obtains the new parameter value and the old parameter value according to the parameter information during execution, which is specifically used to: when it is determined that the type of the write statement request includes an update statement, the parameter information is used as the old parameter value; Obtain the new parameter value based on the update statement and the old parameter value.
  • the sub-execution plan tree obtaining module obtains the new parameter value and the old parameter value according to the parameter information during execution, specifically used for: when it is determined that the type of the write statement request includes a delete statement or an insert...select statement, the The parameter information is used as the old parameter value; the new parameter value is set to be the same as the old parameter value.
  • the trigger creation module executes the creation request sent by the client and creates the trigger through the computing node and the storage node, it is specifically used to: receive the creation request sent by the client, where the creation request contains the to-be-created The trigger name and trigger logic of the trigger; determine whether there is a trigger through the computing node, if it exists, directly return the trigger existence instruction, otherwise, create a trigger according to the creation request.
  • the trigger creation module executes the creation of a trigger based on a creation request, it is specifically used to: determine whether the trigger can be pushed down according to the creation request, and if so, send a push creation request to the storage node through the computing node, and store The node creates a trigger according to the push creation request, and returns the metadata corresponding to the trigger to the computing node for storage; otherwise, the computing node directly creates the trigger according to the creation request and saves the metadata corresponding to the trigger.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Object code.
  • ISA instruction set architecture
  • an embodiment of the present application provides a trigger-implemented device, including a memory 501 and a processor 502, the memory 501 stores a program, and the program is read and executed by the processor 502 , To implement the trigger implementation method described in any one of the embodiments.
  • an embodiment of the present application provides a computer-readable storage medium 601.
  • the computer-readable storage medium 601 stores one or more programs 602, and the one or more programs 602 can be used by one or It is executed by multiple processors to implement the trigger implementation method described in any one of the embodiments.
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) DVD or CD) etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FGPA programmable logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Operations Research (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种触发器实现的方法和装置。该方法包括：根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树（11）；合并写语句请求执行计划树和触发器执行计划树，得到写请求触发计划树（12）；执行写请求触发计划树（13）。

Description

一种触发器实现的方法和装置
相关申请的交叉引用
本申请基于申请号为201911183347.3、申请日为2019年11月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请涉及数据库技术领域，具体涉及一种触发器实现的方法和装置。
背景技术
触发器是数据库提供给程序员和分析员来保证数据完整性的一种方法，它是与表事件相关的特殊的存储过程，它的执行不是由程序调用，而是由事件来触发，比如当对一个表进行操作时就会激活它执行。
目前，分布式数据库还不支持触发器，但在一些应用场景业务线中又急需触发器的功能，从而影响分布式数据库的功能特性，以及用户的体验效果。
发明内容
本申请实施例提供了一种触发器实现的方法，包括：根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树；合并写语句请求执行计划树和触发器执行计划树，得到写请求触发计划树；执行写请求触发计划树。
本申请实施例提供了一种触发器实现的装置，包括：子执行计划树获取模块，用于根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树；写请求触发计划树获取模块，用于合并写语句请求执 行计划树和触发器执行计划树，得到写请求触发计划树；触发计划树执行模块，用于执行写请求触发计划树。
本申请实施例提供了触发器实现的设备，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述的触发器实现的方法。
本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，实现上述的触发器实现的方法。
附图说明
图1是本申请实施例提供的触发器实现的方法流程示意图；
图2是本申请实施例提供的创建触发器交互时序图；
图3是本申请实施例提供的触发器触发执行语句请求的交互时序图；
图4是本申请实施例提供的触发器实现的装置结构示意图。
图5是本申请实施例提供的触发器实现的装置示意图。
图6为本申请实施例提供的存储介质框图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
如图1所示，本申请提供的一种触发器实现的方法流程示意图。该方法可以适用于通过触发器触发执行语句请求的情况。该方法可以由本申请提供的触发器实现的装置执行，该触发器实现的装置由软件和/或硬件实现，并集成在一个设备上。
如图1所示，本申请实施方式提供的一种触发器实现的方法流程示意图， 该方法可以包括：
步骤11，根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树。
在一个示例中，根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树，可以包括：根据写语句请求的类型获取新参数值和旧参数值；根据新参数值、旧参数值和触发器对应的元数据获得触发器执行计划树；根据写语句请求的类型直接获得写语句请求执行计划树。
在一个示例中，分布式数据库包括：计算节点和存储节点，其中，计算节点和存储节点之间进行信令交互。
在一个示例中，根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树之前，还可以包括：根据客户端发送的创建请求，通过计算节点和存储节点创建触发器；将触发器对应的元数据在计算节点进行保存。
在一个示例中，写语句请求的类型包括第一类写语句请求和第二类写语句请求，其中，第一类写语句请求包括插入(insert)语句，第二类写语句请求包括更新(update)语句、删除(delete)语句或插入(insert)...选取(select)语句。
在一个示例中，根据写语句请求的类型获取新参数值和旧参数值，包括：在确定写语句请求的类型包括insert语句时，则直接获取insert语句中所包含的参数信息，并将参数信息作为旧参数值；设置新参数值与旧参数值相同。
在一个示例中，根据写语句请求的类型获取新参数值和旧参数值，可以包括：在确定写语句请求的类型包括第二类写语句请求时，则向存储节点中发送获取数据请求，并接收存储节点根据获取数据请求所返回的参数信息；根据参数信息获取新参数值和旧参数值。
在一个示例中，根据参数信息获取新参数值和旧参数值，可以包括：在确定写语句请求的类型包括update语句时，则将参数信息作为旧参数值；根据 update语句和旧参数值获得新参数值。
在一个示例中，根据参数信息获取新参数值和旧参数值，可以包括：在确定写语句请求的类型包括delete语句或insert...select语句时，则将参数信息作为旧参数值；设置新参数值与旧参数值相同。
在一个示例中，根据客户端发送的创建请求，通过计算节点和存储节点创建触发器，可以包括：接收客户端发送的创建请求，其中，创建请求中包含待创建的触发器名称和触发器逻辑；通过计算节点确定是否存在触发器，若存在，则直接返回触发器存在指令，否则，根据创建请求创建触发器。
在一个示例中，根据创建请求创建触发器，可以包括：根据创建请求判断触发器是否可以下压，若是，则通过计算节点向存储节点发送下压创建请求，存储节点根据下压创建请求创建触发器，并将触发器对应的元数据返回给计算节点进行保存；否则，计算节点直接根据创建请求创建触发器，并将触发器对应的元数据进行保存。
步骤12，合并写语句请求执行计划树和触发器执行计划树，得到写请求触发计划树。
在一个示例中，本申请实施方式中可以将上述所得到的写语句请求执行计划树与所得到的触发器执行计划树合并，即将触发器本身所包含的处理逻辑添加到写语句请求本身所包含的处理逻辑中，从而得到写请求触发计划树。
需要说明的是，在触发器执行计划树中可以包含触发时间，例如之前/之后(before/after)；可以包含监视事件，例如insert/update/delete；可以包含触发事件，例如insert/update/delete，还可以包含监视地点，例如表(table)等，当然，本实施方式中仅是举例进行说明，而并不限定触发器所包含信息的具体内容。
步骤13，执行写请求触发计划树。
具体的说，在本申请实施方式中，在获得写请求触发计划树后，分布式数据库可以通过执行写请求触发计划树中所包含的处理逻辑，对客户端所发送的写语句请求进行执行，从而实现了触发器在分布式数据库中的应用。
例如，当触发器中包含的触发事件为update，触发时间为after，监控事件为update，监控地点为table1，则当写语句请求中包含table1和update时，则在确定执行update事件之后，执行按照指定的table1从分布式数据库中获取数据，并执行相应的操作。
本申请实施例公开的触发器实现的方法，在执行写语句请求时，能够在原写语句请求的执行逻辑中加入触发器的执行逻辑，并通过新组成的执行计划对原写语句请求进行执行，从而在分布式数据库的基础上实现了触发器的应用，增强了分布式数据库的功能特性，提高了用户的体验效果。
如图2所示，本申请实施方式提供的创建触发器交互时序图。其中，Client表示客户端，Proxy表示计算节点，DB表示存储节点，计算节点和存储节点组成分布式数据库，并且本申请实施方式中在执行语句请求之前，分布式数据库可以通过计算节点和存储节点根据客户端的创建请求创建触发器。
需要说明的是，本实施方式中的分布式数据库中还可以包括其它类型的节点，如管理节点，计算节点在将触发器对应的元数据进行保存主要指的缓存，而管理节点是用于实现元数据的最终保存，当然，管理节点还可以具有其他应用，由于管理节点的其他应用并不是本申请的重点，所以本实施方式中不再对其进行赘述。
101：Proxy接收Client发送的创建请求。
其中，创建请求中包含待创建的触发器名称和触发器逻辑，当然，在创建请求中还包含待创建的触发器的属性信息，属性信息可以包含下压信息或非下压信息，本实施方式中仅是举例说明，对于其它类型的属性信息也是在本申请的保护范围内的，本申请实施方式中不再进行赘述。
102：判断是否已经存在触发器。
通过计算节点Proxy根据触发器名称从分布式数据库中的表信息中进行查询，确定是否存在相同名称的触发器，若存在，则执行103，否则，执行104。
103：创建请求回复。
Proxy向Client返回创建请求回复，该创建请求回复中包含存在相同名称的触发器指示信息。
104：判断是否可以下压。
Client在经过查询确定不存在相同名称的触发器时，会根据创建请求创建触发器。在创建触发器时会根据创建请求中所包含的属性信息判断触发器是否可以下压，若可以下压，则执行105，否则，执行107。
105：向DB发送下压创建请求。
其中，在确定可以下压的情况下则通过计算节点Proxy向存储节点DB发送下压创建请求，存储节点DB根据下压创建请求创建触发器，在创建完成的情况下会执行106。
106：DB创建请求回复。
其中，DB在触发器创建完成的情况下会向Proxy反馈创建请求回复，并将触发器对应的元数据反馈给Proxy进行保存。
107：存储元数据。
其中，在确定不可以下压的情况下则Proxy直接根据创建请求创建触发器并将触发器对应的元数据进行保存。
需要说明的是，根据105和107可以看出，针对待创建的触发器的下压情况，分布式数据库中执行创建触发器的主体是存在区别的，在确定可以下压的情况下，执行创建动作的执行主体是DB，在确定不可以下压的情况下，执行创建动作的执行主体是Proxy，但不论执行创建动作的执行主体是DB还是Proxy，创建出来的触发器所对应的元数据都会在Proxy中进行保存。
108：创建请求回复。
Proxy向Client返回创建请求回复，该创建请求回复中包含触发器已经创建完成的指示信息。
如图3所示，为本申请实施方式提供的触发器触发执行语句请求的交互时序图。
201：Proxy接收Client发送的写语句请求。
其中，客户端Client发送给计算节点Proxy的写语句请求的类型包括第一类写语句请求和第二类写语句请求，其中，第一类写语句请求包括insert语句，第二类写语句请求包括update语句、delete语句或insert...select语句，在图3中针对步骤201用字母Insert来表示insert和insert...select这两种类型的写语句请求。
需要说明的是，本申请实施方式中的写语句请求中还包含写表表名，即写语句需要针对分布式数据库中的哪个表进行操作。
202：判断是否已经存在触发器。
Proxy会根据写语句请求中包含的写表表名在所保存的元数据中进行查询，判断是否存在相应的触发器，若不存在，则执行203，若存在，则执行204
203：写语句请求回复。
其中，Proxy在确定触发器不存在的情况下，仅会根据写语句请求生成写语句请求执行计划树，根据写语句请求执行计划树对写语句请求进行执行后，向写客户端Client反馈写语句请求回复，由于触发器不存在的情况下并不是本申请的重点，因此本实施方式中不再进行赘述。
204：获取触发器元数据
其中，Proxy在确定触发器存在的情况下，会提取之前所保存的触发器元数据，元数据中包含针对该触发器所设定的执行逻辑。
205：向DB下发select…for update请求。
需要说明的是，在确定存在触发器的情况下需要构建触发器执行计划树，而在构建触发器执行计划树时，具体是根据写语句请求的类型获取新参数值和旧参数值；根据新参数值、旧参数值和触发器对应的元数据获得触发器执行计划树。
针对新参数值和旧参数值的获取，Proxy根据第二类写语句请求包括update语句、delete语句或insert...select语句，需要向DB下发select...for update请求 获取到相关参数信息，并通过执行206至208从相关参数信息中确定出新参数值和旧参数值，而Proxy根据第一类写语句请求insert语句可以直接执行209来获得，无需向DB发送请求来获取参数信息。
206：select回复。
其中，DB在获取到Proxy发送的请求信息后，会根据请求向Proxy反馈请求信息中所需要获取的相关参数信息。
207：将select上来的参数信息和写语句请求计算新参数值。
针对写语句请求的类型不同，根据参数信息获取新参数值和旧参数值的具体方式也是存在区别的，在确定写语句请求的类型包括update语句时，则将从DB中所获取的参数信息作为旧参数值；根据update语句和旧参数值计算出新参数值。
208：将select上来的参数信息作为旧参数值，新参数值设置成与旧参数值相同。
其中，在确定写语句请求的类型包括delete语句或insert...select语句时等非update语句时，则将参数信息作为旧参数值，并设置新参数值与旧参数值相同。
209：将写语句请求中直接获取的参数信息作为旧参数值，新参数值和旧参数值相同。
其中，在确定写语句请求的类型包括insert语句时，则直接从insert语句中获取所包含的参数信息，并将参数信息作为旧参数值。
210：根据新参数值、旧参数值和触发器元数据生成触发器执行计划树。
其中，在获取的新参数值、旧参数值和触发器元数据之后，可以将新参数值、旧参数值添加到触发器元数据中，得到包含触发器处理逻辑的触发器执行计划树。
211：根据写语句请求生成写语句请求执行计划树。
其中，Proxy会根据写语句请求生成写语句请求执行计划树，写语句请求 执行计划树中包含原写语句请求所包含的处理逻辑。
212：将触发器执行计划树和写语句请求执行计划树合并生成写请求触发计划树。
其中，本实施方式中将触发器执行计划树和写语句请求执行计划树进行合并，即将触发器包含的处理逻辑添加到原写语句请求所包含的处理逻辑中，从而实现触发器在分布式数据库的应用。
213：按照写请求触发计划树将写语句请求发送至DB。
其中，Proxy会按照请求触发计划树中所包含的新的处理逻辑将写语句请求发送到DB中，并由DB进行执行。
214：返回执行结果。
DB在对写语句请求处理后会将处理结果反馈给Proxy。
215：写语句请求回复。
Proxy将DB所反馈的处理结果发送给Client，以对Client所发送的写语句请求进行结果回复。
图4示出本申请实施例的触发器实现的装置结构示意图，如图4所示，该装置包括：子执行计划树获取模块41，用于根据写语句请求的类型确定写语句请求执行计划树和与写语句请求对应的触发器执行计划树；写请求触发计划树获取模块42，用于合并写语句请求执行计划树和触发器执行计划树，得到写请求触发计划树；触发计划树执行模块43，用于执行写请求触发计划树。
本实施例提供的触发器实现的装置用于实现本申请的触发器实现的方法，本实施例提供的触发器实现的装置实现原理和技术效果与本申请的触发器实现的方法类似。本申请实施例公开的触发器实现的装置，在执行写语句请求时，能够在原写语句请求的执行逻辑中加入触发器的执行逻辑，并通过新组成的执行计划对原写语句请求进行执行，从而在分布式数据库的基础上实现了触发器的应用，增强了分布式数据库的功能特性，提高了用户的体验效果。
在一个示例中，子执行计划树获取模块，具体用于：根据写语句请求的类 型获取新参数值和旧参数值；根据新参数值、旧参数值和触发器对应的元数据获得触发器执行计划树；根据写语句请求的类型直接获得写语句请求执行计划树。
在一个示例中，分布式数据库包括：计算节点和存储节点，其中，计算节点和存储节点之间进行信令交互。
在一个示例中，还包括：触发器创建模块，用于：根据客户端发送的创建请求，通过计算节点和存储节点创建触发器；将触发器对应的元数据在计算节点进行保存。
在一个示例中，写语句请求的类型包括第一类写语句请求和第二类写语句请求，其中，第一类写语句请求包括insert语句，第二类写语句请求包括update语句、delete语句或insert...select语句。
在一个示例中，子执行计划树获取模块在执行根据写语句请求的类型获取新参数值和旧参数值时，具体用于：在确定写语句请求的类型包括insert语句时，则直接获取insert语句中所包含的参数信息，并将参数信息作为旧参数值；设置新参数值与旧参数值相同。
在一个示例中，子执行计划树获取模块在执行根据写语句请求的类型获取新参数值和旧参数值时，具体用于：在确定写语句请求的类型包括第二类写语句请求时，则向存储节点中发送获取数据请求，并接收存储节点根据获取数据请求所返回的参数信息；根据参数信息获取新参数值和旧参数值。
在一个示例中，子执行计划树获取模块在执行根据参数信息获取新参数值和旧参数值，具体用于：在确定写语句请求的类型包括update语句时，则将参数信息作为旧参数值；根据update语句和旧参数值获得新参数值。
在一个示例中，子执行计划树获取模块在执行根据参数信息获取新参数值和旧参数值，具体用于：在确定写语句请求的类型包括delete语句或insert...select语句时，则将参数信息作为旧参数值；设置新参数值与旧参数值相同。
在一个示例中，触发器创建模块在执行根据客户端发送的创建请求，通过 计算节点和存储节点创建触发器时，具体用于：接收客户端发送的创建请求，其中，创建请求中包含待创建的触发器名称和触发器逻辑；通过计算节点确定是否存在触发器，若存在，则直接返回触发器存在指令，否则，根据创建请求创建触发器。
在一个示例中，触发器创建模块在执行根据创建请求创建触发器时，具体用于：根据创建请求判断触发器是否可以下压，若是，则通过计算节点向存储节点发送下压创建请求，存储节点根据下压创建请求创建触发器，并将触发器对应的元数据返回给计算节点进行保存；否则，计算节点直接根据创建请求创建触发器，并将触发器对应的元数据进行保存。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
如图5所示，本申请的实施例提供一种触发器实现的设备，包括存储器501和处理器502，所述存储器501存储有程序，所述程序在被所述处理器502读取执行时，实现任一实施例所述的触发器实现的方法。
如图6所示，本申请一实施例提供一种计算机可读存储介质601，所述计算机可读存储介质601存储有一个或者多个程序602，所述一个或者多个程序602可被一个或者多个处理器执行，以实现任一实施例所述的触发器实现的方法。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和 功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和系统(数码多功能光碟DVD或CD光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、可编程逻辑器件(FGPA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本发明的范围。因此，本发明的恰当范围将根据权利要求确定。

Claims (14)

  1. 一种触发器实现的方法，应用于分布式数据库，其中，包括：
    根据写语句请求的类型确定写语句请求执行计划树和与所述写语句请求对应的触发器执行计划树；
    合并所述写语句请求执行计划树和所述触发器执行计划树，得到写请求触发计划树；
    执行所述写请求触发计划树。
  2. 根据权利要求1所述的方法，所述根据写语句请求的类型确定写语句请求执行计划树和与所述写语句请求对应的触发器执行计划树，包括：
    根据所述写语句请求的类型获取新参数值和旧参数值；
    根据所述新参数值、所述旧参数值和所述触发器对应的元数据获得所述触发器执行计划树；
    根据所述写语句请求的类型直接获得所述写语句请求执行计划树。
  3. 根据权利要求2所述的方法，其中，所述分布式数据库包括：计算节点和存储节点，其中，所述计算节点和所述存储节点之间进行信令交互。
  4. 根据权利要求3所述的方法，其中，所述根据写语句请求的类型确定写语句请求执行计划树和与所述写语句请求对应的触发器执行计划树之前，还包括：
    根据客户端发送的创建请求，通过所述计算节点和所述存储节点创建所述触发器；
    将所述触发器对应的所述元数据在所述计算节点进行保存。
  5. 根据权利要求4所述的方法，其中，所述写语句请求的类型包括第一类写语句请求和第二类写语句请求，
    其中，所述第一类写语句请求包括insert语句，所述第二类写语句请求包括update语句、delete语句或insert...select语句。
  6. 根据权利要求5所述的方法，其中，所述根据所述写语句请求的类型获 取新参数值和旧参数值，包括：
    在确定所述写语句请求的类型包括所述insert语句时，则直接获取所述insert语句中所包含的参数信息，并将所述参数信息作为所述旧参数值；
    设置所述新参数值与所述旧参数值相同。
  7. 根据权利要求5所述的方法，其中，所述根据所述写语句请求的类型获取新参数值和旧参数值，包括：
    在确定所述写语句请求的类型包括所述第二类写语句请求时，则向所述存储节点中发送获取数据请求，并接收所述存储节点根据所述获取数据请求所返回的参数信息；
    根据所述参数信息获取所述新参数值和所述旧参数值。
  8. 根据权利要求7所述的方法，其中，所述根据所述参数信息获取所述新参数值和所述旧参数值，包括：
    在确定所述写语句请求的类型包括所述update语句时，则将所述参数信息作为所述旧参数值；
    根据所述update语句和所述旧参数值获得所述新参数值。
  9. 根据权利要求7所述的方法，其中，所述根据所述参数信息获取所述新参数值和所述旧参数值，包括：
    在确定所述写语句请求的类型包括所述delete语句或insert...select语句时，则将所述参数信息作为所述旧参数值；
    设置所述新参数值与所述旧参数值相同。
  10. 根据权利要求4所述的方法，其中，所述根据客户端发送的创建请求，通过所述计算节点和所述存储节点创建所述触发器，包括：
    接收所述客户端发送的创建请求，其中，所述创建请求中包含待创建的触发器名称和触发器逻辑；
    通过所述计算节点确定是否存在所述触发器，若存在，则直接返回触发器存在指令，若不存在，根据所述创建请求创建所述触发器。
  11. 根据权利要求10所述的方法，所述根据所述创建请求创建所述触发器，包括：
    根据所述创建请求判断所述触发器是否可以下压，若是，则通过所述计算节点向所述存储节点发送下压创建请求，所述存储节点根据所述下压创建请求创建所述触发器，并将所述触发器对应的所述元数据返回给所述计算节点进行保存；
    若所述触发器不可以下压，所述计算节点直接根据所述创建请求创建所述触发器，并将所述触发器对应的所述元数据进行保存。
  12. 一种触发器实现的装置，包括：
    子执行计划树获取模块，用于根据写语句请求的类型确定写语句请求执行计划树和与所述写语句请求对应的触发器执行计划树；
    写请求触发计划树获取模块，用于合并所述写语句请求执行计划树和所述触发器执行计划树，得到写请求触发计划树；
    触发计划树执行模块，用于执行所述写请求触发计划树。
  13. 一种触发器实现的设备，包括：
    存储器；和
    处理器；其中所述存储器存储计算机程序，所述计算机程序在被所述处理器执行时，实现权利要求1～11任一项所述的触发器实现的方法。
  14. 一种计算机可读存储介质，所述计算机可读存储介质存储计算机程序，所述计算机程序被处理器执行时，实现权利要求1～11任一项所述的触发器实现的方法。
PCT/CN2020/126580 2019-11-27 2020-11-04 一种触发器实现的方法和装置 WO2021103969A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20891959.7A EP4050495A4 (en) 2019-11-27 2020-11-04 METHOD AND DEVICE FOR TRIGGER IMPLEMENTATION

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911183347.3 2019-11-27
CN201911183347.3A CN112860740B (zh) 2019-11-27 2019-11-27 一种触发器实现的方法和装置

Publications (1)

Publication Number Publication Date
WO2021103969A1 true WO2021103969A1 (zh) 2021-06-03

Family

ID=75984867

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/126580 WO2021103969A1 (zh) 2019-11-27 2020-11-04 一种触发器实现的方法和装置

Country Status (3)

Country Link
EP (1) EP4050495A4 (zh)
CN (1) CN112860740B (zh)
WO (1) WO2021103969A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114327414B (zh) * 2022-01-25 2022-11-15 重庆允丰科技有限公司 节点可插拨的触发器实现方法及计算机可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143745A1 (en) * 2001-03-29 2002-10-03 Eliezer Levy Method of parallel trigger execution in an active database
US20070083545A1 (en) * 2005-10-12 2007-04-12 Erwin Pinter Selectively triggering events
CN101256577A (zh) * 2008-03-18 2008-09-03 中兴通讯股份有限公司 一种嵌入式数据库中触发器的实现方法
CN102289433A (zh) * 2010-06-18 2011-12-21 中兴通讯股份有限公司 一种实现数据库触发器功能的方法及装置
CN104462078A (zh) * 2013-09-12 2015-03-25 方正信息产业控股有限公司 一种xml数据库触发器的实现方法、装置及xml数据库
CN107798017A (zh) * 2016-09-07 2018-03-13 南京中兴新软件有限责任公司 分布式数据库中的执行计划信息生成方法和系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063331B (zh) * 2014-07-03 2017-04-12 龙芯中科技术有限公司 处理器、共享存储区域访问方法和锁管理器
CN105608086B (zh) * 2014-11-17 2021-07-27 中兴通讯股份有限公司 分布式数据库系统的事务处理方法及装置
CN105677683B (zh) * 2014-11-21 2018-12-14 华为技术有限公司 批量数据查询方法和装置
CN107229628B (zh) * 2016-03-23 2022-02-01 金篆信科有限责任公司 分布式数据库预处理的方法及装置
CN109885585B (zh) * 2019-02-18 2020-01-10 星环信息科技（上海）有限公司 支持存储过程、触发器与视图的分布式数据库系统和方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143745A1 (en) * 2001-03-29 2002-10-03 Eliezer Levy Method of parallel trigger execution in an active database
US20070083545A1 (en) * 2005-10-12 2007-04-12 Erwin Pinter Selectively triggering events
CN101256577A (zh) * 2008-03-18 2008-09-03 中兴通讯股份有限公司 一种嵌入式数据库中触发器的实现方法
CN102289433A (zh) * 2010-06-18 2011-12-21 中兴通讯股份有限公司 一种实现数据库触发器功能的方法及装置
CN104462078A (zh) * 2013-09-12 2015-03-25 方正信息产业控股有限公司 一种xml数据库触发器的实现方法、装置及xml数据库
CN107798017A (zh) * 2016-09-07 2018-03-13 南京中兴新软件有限责任公司 分布式数据库中的执行计划信息生成方法和系统

Also Published As

Publication number Publication date
EP4050495A4 (en) 2022-11-30
CN112860740B (zh) 2022-12-20
CN112860740A (zh) 2021-05-28
EP4050495A1 (en) 2022-08-31

Similar Documents

Publication Publication Date Title
US9141510B2 (en) Memory allocation tracking
CN107016016B (zh) 一种数据处理的方法及装置
JP2004362596A5 (zh)
WO2020093501A1 (zh) 文件存储方法、删除方法、服务器及存储介质
CN110046170B (zh) 基于多文件管理的语句执行方法、装置、设备和介质
US10387372B2 (en) Value-based differential data
Domaschka et al. Reliability and availability properties of distributed database systems
WO2018120233A1 (zh) 一种事务处理方法及装置
CN110188114A (zh) 一种数据操作的优化方法、装置、系统、设备和存储介质
US11720607B2 (en) System for lightweight objects
WO2021103969A1 (zh) 一种触发器实现的方法和装置
CN112416710A (zh) 用户操作的记录方法、装置、电子设备及存储介质
US11704114B2 (en) Data structures for managing configuration versions of cloud-based applications
CN107609131B (zh) 一种报表文件生成方法及装置
WO2020119709A1 (zh) 数据合并的实现方法、装置、系统及存储介质
CN108334333B (zh) 一种源代码库更新方法及装置
CN110866011A (zh) 数据表同步方法、装置、计算机设备和存储介质
CN112000971B (zh) 一种文件权限记录方法、系统及相关装置
US10817272B2 (en) Generation and usage of language-converted script
CN112988701A (zh) 数据库管理方法、装置、系统和存储介质
US9009731B2 (en) Conversion of lightweight object to a heavyweight object
US11366658B1 (en) Seamless lifecycle stability for extensible software features
US20220237151A1 (en) Fast and efficient storage system implemented with multiple cloud services
CN109034982B (zh) 千万级订单表中订单信息加速处理方法及装置
JP2022551454A (ja) ストアドプロシージャの実行方法、装置、データベースシステム及び記憶媒体

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20891959

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020891959

Country of ref document: EP

Effective date: 20220527

NENP Non-entry into the national phase

Ref country code: DE