CN114327795A - Database transaction consistency processing method and device in cross-link calling - Google Patents
Database transaction consistency processing method and device in cross-link calling Download PDFInfo
- Publication number
- CN114327795A CN114327795A CN202111617908.3A CN202111617908A CN114327795A CN 114327795 A CN114327795 A CN 114327795A CN 202111617908 A CN202111617908 A CN 202111617908A CN 114327795 A CN114327795 A CN 114327795A
- Authority
- CN
- China
- Prior art keywords
- database
- sqlsession
- script
- link
- business service
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A database transaction consistency processing method and device in cross-link calling are disclosed, when a service executes a script container, SqlSession executed by the current script container is obtained and stored; if the database operation exists in the script container, calling the business service through the script container, and executing the corresponding database operation by the business service through the stored SqlSession; returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operations; and the script container returns the script execution result to the business service, and the stored SqlSession is cleared. The invention can serve the script container, ensure the data consistency in the cross-service call link by completely depending on database affairs, simplify the development flow of cross-link call, ensure that all database operations in the same script are under the same affair, and improve the development efficiency.
Description
Technical Field
The invention relates to a method and a device for processing database transaction consistency in cross-link calling, and belongs to the technical field of database processing.
Background
With the popularity of distributed service architecture, especially the application of design concepts such as micro-services to the system, the system architecture becomes more and more distributed. The distributed call tracking technology completely connects the calling process of one request in series in a call chain mode, and further realizes the monitoring of the calling path of the request.
A database transaction is a sequence of database operations that access and potentially manipulate various data items, either all or none of which are an indivisible unit of work, the transaction consisting of all database operations performed between the beginning of the transaction and the end of the transaction.
Currently, strong consistency of database transactions is achieved by using the method of Saga invoking rollback on error reporting. Because the processing mode of the transaction occurring in the cross-link call is complex, if distributed transactions such as Saga and the like are used, once an error is reported, a rollback interface of the template service may be required to be called, so that the development process is complicated. How to guarantee that all database operations in the same script are under the same transaction is a technical problem to be solved.
Disclosure of Invention
Therefore, the invention provides a method and a device for processing the consistency of database transactions in cross-link calling, which can ensure the consistency of data in cross-service calling links, ensure that all database operations in the same script are under the same transaction, and improve the development efficiency.
In order to achieve the above purpose, the invention provides the following technical scheme: a method for processing consistency of database transactions in cross-link calling comprises the following steps:
when the business service executes the script container, acquiring and storing the SqlSession when the current script container is executed;
if the script container has database operation, calling the business service through the script container, and executing the corresponding database operation by the business service through the stored SqlSession;
returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operations;
and the script container returns the script execution result to the business service, and the stored SqlSession is cleared.
As a preferred scheme of the database transaction consistency processing method in cross-link calling, the current SqlSession link is stored through a link storage pool in the SqlSession process when the current script container is executed is obtained and stored.
As a preferred scheme of the database transaction consistency processing method in the cross-link call, when the business service executes the corresponding database operation report error through the stored sqlSession, the business service rolls back through the @ Transactional annotation and detects whether the @ Transactional annotation is added in the executing process.
As a preferred scheme of the database transaction consistency processing method in cross-link calling, when the service is started, all basemappers under the current service are acquired, traversal analysis is performed, and corresponding table information is stored in a ConcurrentHashMap for subsequent calling.
As an optimal scheme of a database transaction consistency processing method in cross-link calling, a table name is introduced when database operation is carried out, corresponding table information is searched in ConcurrentHashMap through the table name, and if the corresponding table information is not searched, exception is thrown out; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
As a preferred scheme of the database transaction consistency processing method in cross-link calling, the business service allows database operation after passing security verification, and if the security verification fails, the exception is thrown out and the preamble operation is rolled back.
The invention also provides a database transaction consistency processing device in cross-link calling, which comprises:
the system comprises a link acquisition module, a service processing module and a service processing module, wherein the link acquisition module is used for acquiring and storing SqlSession when a current script container is executed by a service;
the calling execution module is used for calling the business service through the script container if the database operation exists in the script container, and the business service executes the corresponding database operation through the stored SqlSession;
the first result returning module is used for returning the database execution result of the database operation to the script container so that the script container continues to execute subsequent database operations;
and the second result returning module is used for returning the script execution result to the service by the script container and clearing the stored SqlSession.
As a preferred scheme of the database transaction consistency processing device in the cross-link call, the link obtaining module obtains and stores the current sqlSession link in the SqlSession process when the current script container is executed, and stores the current sqlSession link through the link storage pool.
As a preferred scheme of the database transaction consistency processing device in the cross-link call, the device further includes a rollback annotation module, configured to, when the business service performs a corresponding database operation error report through the stored SqlSession, perform rollback through the @ Transactional annotation by the business service, and detect whether the @ Transactional annotation is added in an execution process.
The system further comprises a traversal analysis module used for acquiring all basemappers under the current business service when the business service is started, performing traversal analysis and storing corresponding table information into ConcurrentHashMap for subsequent calling.
As a preferred scheme of the database transaction consistency processing device in the cross-link call, the device further comprises a lookup processing module, wherein the lookup processing module is used for transmitting the table name when the database operation is carried out, looking up the corresponding table information in the ConcurrentHashMap through the table name, and throwing out the exception if the corresponding table information is not looked up; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
As a preferred scheme of the database transaction consistency processing device in the cross-link call, the device further comprises a verification processing module, which is used for allowing the database operation after the business service passes the security verification, and if the security verification fails, the exception is thrown out and the preamble operation is rolled back.
The invention has the following advantages: when the business service executes the script container, acquiring and storing the SqlSession when the current script container is executed; if the script container has database operation, calling the business service through the script container, and executing the corresponding database operation by the business service through the stored SqlSession; returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operations; and the script container returns the script execution result to the business service, and the stored SqlSession is cleared. The invention can serve the script container, ensure the data consistency in the cross-service call link by completely depending on the database affairs, simplify the development flow of cross-link call, and ensure that all database operations in the same script are under the same affair; the invention provides a database operation function for the script container service, increases the use scenes of the script container, can meet more requirements, further avoids the creation of a second-opening project, is convenient to simplify the service logic and improves the development efficiency.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so that those skilled in the art can understand and read the present invention, and do not limit the conditions for implementing the present invention, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the functions and purposes of the present invention, should still fall within the scope of the present invention.
Fig. 1 is a technical route diagram of a method for processing consistency of database transactions in a cross-link call according to embodiment 1 of the present invention;
fig. 2 is a flowchart of a method for processing consistency of database transactions in a cross-link call according to embodiment 1 of the present invention;
fig. 3 is a schematic diagram of a device for processing consistency of database transactions in cross-link calls according to embodiment 2 of the present invention.
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
Referring to fig. 1 and fig. 2, embodiment 1 of the present invention provides a method for processing consistency of database transactions in cross-link calls, including the following steps:
s1, when the service executes the script container, acquiring and storing the SqlSession when the current script container is executed;
s2, if the database operation exists in the script container, calling the business service through the script container, and executing the corresponding database operation through the stored SqlSession by the business service;
s3, returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operation;
and S4, the script container returns the script execution result to the service, and the stored SqlSession is cleared.
In this embodiment, when the business service executes a script container, the business service executes an effective SQL and obtains a SQL session currently executed. Next, if a database operation is required in the script, the script container calls the service, the service executes the corresponding database operation through the previously stored sqlsessension, and returns the result to the script container service, so that the script container can continue to execute subsequent operations, and if there are multiple database operations in the subsequent operation, the current step is repeated. And finally, the script container returns the script execution result to the service and cleans up the stored Sqlsessession.
In this embodiment, in the process of obtaining and storing the SqlSession when the current script container is executed, the current SqlSession link is stored through the link storage pool.
Specifically, the SqlSession is one of the most important constructions of Mybatis, and when the Mybatis is used for transaction submission, the transaction is submitted by calling the SqlSession. It can be considered that a series of configurations of Mybatis aims to generate a SqlSession object similar to a link object generated by Jdbc, so that the Mybatis can communicate with a database, and the addition, deletion, modification and checking can be realized through the SqlSession.
In this embodiment, when the business service executes the corresponding database operation through the stored SqlSession and reports an error, the business service rolls back through the @ Transactional annotation and detects whether the @ Transactional annotation is added in the execution process.
Specifically, @ transaction in Spring is a dynamic proxy-based mechanism, and provides a transparent transaction management mechanism, so that the problem encountered in development can be conveniently and quickly solved. @ Transactional can act on interfaces, interface methods, classes, and class methods, when acting on a class, all public methods of the class will have the transaction attribute of the type, and at the same time, the label can be used at the method level to override the definition of the class level.
In this embodiment, when the service is started, all basemappers under the current service are acquired, traversal analysis is performed, and corresponding table information is stored in the ConcurrentHashMap for subsequent call.
Specifically, when the business service is started, by rewriting an applicable event method in an applicable Listener, all baseMapper under the current business service is obtained by using a getConfiguration (). getMapper registration (). getMapper () method provided in SqlSessionFactory during starting, and the corresponding table information (including column information, a main key and the like) is traversed and analyzed and stored in a ConcurrentHashMap for subsequent calling.
Specifically, the ConcurrentHashMap is an important member of j.u.c (java.util.current package), and is a thread-safe and efficient concurrency-supported version of the HashMap. The ConcurrentHashMap may support 16 threads to perform concurrent writes and any number of threads to read.
Specifically, the ApplicationContext event mechanism is an implementation of observer design mode, and the ApplicationContext event processing can be implemented through an applicationevent class and an ApplicationListener interface.
Specifically, the SqlSessionFactory is a key object of MyBatis and is a memory mirror image of a single database mapping relationship after compiling, and an instance of the SqlSessionFactory object can be obtained through the SqlSessionFactoryBuilder object class.
In particular, the baseMapper interface is known under the fully qualified name com.
In this embodiment, a table name is introduced when a database operation is performed, corresponding table information is looked up in the ConcurrentHashMap by the table name, and if the corresponding table information is not looked up, an exception is thrown out; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
Specifically, the table name is used to look up the corresponding table information in the ConcurrentHashMap, and if the table name is not found, the next operation cannot be performed, so that the exception needs to be thrown out. And finally, traversing whether the field needing to be operated exists or not, and carrying out corresponding increasing, deleting, modifying and checking operations.
In the embodiment, the whole set of operations can be executed by the server, and the execution result is returned to the script container and then executed in the next step, so that all the operations can be ensured to be in the same transaction, and the transaction depending on the database has higher reliability.
In this embodiment, the service allows the database operation after passing the security verification, and if the security verification fails, throws out the exception and rolls back the preamble operation.
Specifically, since the database can be operated through the script container, the data security problem needs to be considered: data of non-local tenants should not be queried; data of non-tenants cannot be newly added; data of non-tenants should not be deleted and changed; tables without tenant identities cannot be queried in this way.
And traversing and checking the field needing to be operated in the parameter through the table information stored in the ConcurrentHashMap. And for the business service, at least through the safety verification, the further operation can be carried out, otherwise, the exception is directly thrown out, and the previous operation is rolled back together.
In summary, when the business service executes the script container, the invention obtains and stores the sqlSession executed by the current script container; if the database operation exists in the script container, calling the business service through the script container, and executing the corresponding database operation by the business service through the stored SqlSession; returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operations; and the script container returns the script execution result to the service, and the stored SqlSession is cleared. When the business service executes the corresponding database operation through the stored SqlSession and reports the error, the business service rolls back through the @ Transactional annotation and detects whether the @ Transactional annotation is added in the executing process. When the business service is started, all basemappers under the current business service are obtained, traversal analysis is carried out, and corresponding table information is stored in the ConcurrentHashMap for subsequent calling. When database operation is carried out, a table name is introduced, corresponding table information is searched in the ConcurrentHashMap through the table name, and if the corresponding table information is not searched, exception is thrown out; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field. And after the business service passes the security verification, allowing the database operation, and if the security verification fails, throwing the exception and rolling back the preorder operation. The invention can serve the script container, ensure the data consistency in the cross-service call link by completely depending on the database affairs, simplify the development flow of cross-link call, and ensure that all database operations in the same script are under the same affair; the invention provides a database operation function for the script container service, increases the use scenes of the script container, can meet more requirements, further avoids the creation of a second-opening project, is convenient to simplify the service logic and improves the development efficiency.
Example 2
Referring to fig. 3, embodiment 2 of the present invention further provides a device for processing consistency of database transactions in cross-link calls, including:
the link acquisition module 1 is used for acquiring and storing the SqlSession when the current script container is executed by the business service;
the calling execution module 2 is used for calling the business service through the script container if the database operation exists in the script container, and the business service executes the corresponding database operation through the stored SqlSession;
the first result returning module 3 is used for returning the database execution result of the database operation to the script container, so that the script container continues to execute subsequent database operations;
and the second result returning module 4 is used for returning the script execution result to the service by the script container and cleaning the stored SqlSession.
In this embodiment, the link obtaining module 1 obtains and stores the current SqlSession link in the SqlSession process when the current script container is executed, and stores the current SqlSession link through the link storage pool.
In this embodiment, the system further includes a rollback annotation module 5, configured to, when the business service executes a corresponding database operation through the stored SqlSession and reports an error, detect whether to add the @ Transactional annotation by the business service through the @ Transactional annotation in the execution process.
In this embodiment, the system further includes a traversal analysis module 6, configured to, when the service is started, obtain all basemappers of the current service, perform traversal analysis, and store corresponding table information in the ConcurrentHashMap for subsequent call.
In this embodiment, the system further includes a lookup processing module 7, configured to introduce a table name when performing a database operation, lookup corresponding table information in the convurrenthashmap by the table name, and throw an exception if the corresponding table information is not looked up; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
In this embodiment, the system further includes a verification processing module 8, configured to allow the database operation to be performed after the business service passes the security verification, and if the security verification fails, throw out an exception and roll back the preamble operation.
It should be noted that, because the contents of information interaction, execution process, and the like between the modules/units of the apparatus are based on the same concept as the method embodiment in embodiment 1 of the present application, the technical effect brought by the contents is the same as the method embodiment of the present application, and specific contents may refer to the description in the foregoing method embodiment of the present application, and are not described herein again.
Example 3
The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Example 4
An embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor, the processor calling the program instructions being capable of performing the method of database transaction consistency handling in a cross-link call of embodiment 1 or any possible implementation thereof.
Specifically, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated in the processor, located external to the processor, or stand-alone.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.).
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. A method for processing consistency of database transactions in cross-link calling is characterized by comprising the following steps:
when the business service executes the script container, acquiring and storing the SqlSession when the current script container is executed;
if the script container has database operation, calling the business service through the script container, and executing the corresponding database operation by the business service through the stored SqlSession;
returning the database execution result of the database operation to the script container, and enabling the script container to continue executing subsequent database operations;
and the script container returns the script execution result to the business service, and the stored SqlSession is cleared.
2. The method for processing consistency of database transactions in cross-link call as recited in claim 1, wherein the current sqlSession link is stored through the link storage pool during the SqlSession process when the current script container is executed is obtained and stored.
3. The method as claimed in claim 1, wherein when the business service performs the corresponding database operation error reporting through the stored sqlSession, the business service rolls back through the @ Transactional annotation and detects whether the @ Transactional annotation is added during the execution process.
4. The method according to claim 1, wherein when the service is started, all basemappers of the current service are acquired, and the corresponding table information is stored in a ConcurrentHashMap for subsequent calling after traversal analysis.
5. The method for processing the consistency of the database transactions in the cross-link call as claimed in claim 4, wherein the table name is introduced when the database operation is performed, the corresponding table information is looked up in the ConcurrentHashMap through the table name, and if the corresponding table information is not looked up, the exception is thrown out; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
6. The method according to claim 5, wherein the business service allows database operations after passing security verification, and if the security verification fails, an exception is thrown and the preamble operation is rolled back.
7. An apparatus for processing consistency of database transactions in cross-link calls, comprising:
the system comprises a link acquisition module, a service processing module and a service processing module, wherein the link acquisition module is used for acquiring and storing SqlSession when a current script container is executed by a service;
the calling execution module is used for calling the business service through the script container if the database operation exists in the script container, and the business service executes the corresponding database operation through the stored SqlSession;
the first result returning module is used for returning the database execution result of the database operation to the script container so that the script container continues to execute subsequent database operations;
and the second result returning module is used for returning the script execution result to the service by the script container and clearing the stored SqlSession.
8. The apparatus according to claim 7, wherein the link obtaining module obtains and stores a current SqlSession link in a SqlSession process when the current script container is executed, and stores the current SqlSession link in a linked storage pool.
9. The apparatus according to claim 7, further comprising a rollback annotation module, configured to, when the business service performs the corresponding database operation error report through the stored SqlSession, perform rollback through the @ Transactional annotation by the business service and detect whether to add the @ Transactional annotation during the performing process;
the system also comprises a traversal analysis module, a report module and a report module, wherein the traversal analysis module is used for acquiring all basemappers under the current business service when the business service is started, traversing and analyzing the basemappers and storing corresponding table information into the ConcurrentHashMap for subsequent calling;
the system also comprises a search processing module, a database processing module and a query processing module, wherein the search processing module is used for transmitting the table name when database operation is carried out, searching the corresponding table information in the ConcurrentHashMap through the table name, and throwing the exception if the corresponding table information is not searched; if the corresponding table information is searched, traversing whether the field needing to be operated exists, and performing the operation of increasing, deleting, modifying and checking the corresponding field.
10. The apparatus according to claim 9, further comprising a verification processing module, configured to allow the database operation after the business service passes security verification, and if the security verification fails, throw an exception and roll back a preamble operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111617908.3A CN114327795A (en) | 2021-12-27 | 2021-12-27 | Database transaction consistency processing method and device in cross-link calling |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111617908.3A CN114327795A (en) | 2021-12-27 | 2021-12-27 | Database transaction consistency processing method and device in cross-link calling |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114327795A true CN114327795A (en) | 2022-04-12 |
Family
ID=81014568
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111617908.3A Pending CN114327795A (en) | 2021-12-27 | 2021-12-27 | Database transaction consistency processing method and device in cross-link calling |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114327795A (en) |
-
2021
- 2021-12-27 CN CN202111617908.3A patent/CN114327795A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11907216B2 (en) | Multi-language fusion query method and multi-model database system | |
| US8380759B2 (en) | Type projection query of an instance space | |
| US8521867B2 (en) | Support for incrementally processing user defined aggregations in a data stream management system | |
| US6785674B2 (en) | System and method for structuring data in a computer system | |
| US9772911B2 (en) | Pooling work across multiple transactions for reducing contention in operational analytics systems | |
| CN111522631B (en) | Distributed transaction processing method, device, server and medium | |
| US8732143B2 (en) | Reducing locking during database transactions | |
| EP2797014B1 (en) | Database update execution according to power management schemes | |
| US20210326359A1 (en) | Compare processing using replication log-injected compare records in a replication environment | |
| CN114925084B (en) | Distributed transaction processing method, system, equipment and readable storage medium | |
| US11487742B2 (en) | Consistency checks between database systems | |
| US11474812B1 (en) | Automated data store access source code review | |
| US20130198218A1 (en) | Database Table Partitioning Allowing Overlaps Used in Full Text Query | |
| US10678785B1 (en) | Automated SQL source code review | |
| US10592391B1 (en) | Automated transaction and datasource configuration source code review | |
| US11204746B2 (en) | Encoding dependencies in call graphs | |
| US8799329B2 (en) | Asynchronously flattening graphs in relational stores | |
| CN110737710A (en) | Distributed data automatic structured warehousing method and system | |
| US20230333972A1 (en) | Software testing in parallel with different database instances | |
| CN114327795A (en) | Database transaction consistency processing method and device in cross-link calling | |
| CN115469810A (en) | Data acquisition method, device, equipment and storage medium | |
| US11989180B2 (en) | Proactive query plan compilation | |
| Kvet et al. | Enhancing Analytical Select Statements Using Reference Aliases | |
| US11907217B2 (en) | Database object validation for reusing captured query plans | |
| US20240119071A1 (en) | Relationship-based display of computer-implemented documents |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |