CN114490769A - Database transaction management method, device, equipment and storage medium - Google Patents
Database transaction management method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114490769A CN114490769A CN202210111258.3A CN202210111258A CN114490769A CN 114490769 A CN114490769 A CN 114490769A CN 202210111258 A CN202210111258 A CN 202210111258A CN 114490769 A CN114490769 A CN 114490769A
- Authority
- CN
- China
- Prior art keywords
- database
- transaction
- thread
- connection
- local variable
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 44
- 238000003860 storage Methods 0.000 title claims abstract description 13
- 238000000034 method Methods 0.000 claims abstract description 27
- 238000005096 rolling process Methods 0.000 claims description 7
- 230000002093 peripheral effect Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
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/24553—Query execution of query operations
- G06F16/24558—Binary matching operations
- G06F16/2456—Join operations
-
- 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/21—Design, administration or maintenance of databases
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)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a database transaction management method, a database transaction management device, a database transaction management equipment and a storage medium, and belongs to the technical field of computers. It includes: acquiring a current thread; the current thread is used for executing at least one database transaction; acquiring a thread local variable corresponding to a current thread; the thread local variable comprises at least one database parameter corresponding to the database transaction; determining database connections in thread local variables; acquiring a transaction identifier; setting the affair of the database connected with the corresponding database as an open state under the condition of determining that the affair identifier is a preset identifier; the database connection is traversed and at least one database transaction is executed. The method can solve the problem that the management of the configuration transaction is inconvenient because the transaction of the database is managed by a cut-in mode of a section-oriented programming section, the process of setting the configuration file is complex, and the code is required to be modified.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a database transaction management method, device, equipment and storage medium.
Background
Database transactions refer to a sequence of database operations that access and manipulate various data items, and if a transaction needs to operate on multiple databases, a management mechanism is needed to prevent data rewriting and provide synchronization, and the ability to return stale transactions is also needed to provide security and data recovery capabilities. Therefore, an excellent database transaction management method is crucial.
A conventional database transaction management method includes: by setting a configuration file, database transactions are managed in a cut-through mode of an Aspect Oriented Programming (AOP) cut-in.
However, the transaction of the database is managed by a cut-in mode of a section-oriented programming section, the process of setting the configuration file is complex, and the code is often required to be modified, so that the problem of inconvenience in managing the configuration transaction exists.
Disclosure of Invention
The application provides a database transaction management method, a database transaction management device and a database transaction management storage medium, which can solve the problem that the transaction management is inconvenient due to the fact that a configuration file setting process is complex and codes are required to be modified frequently in a mode of cutting in a section-oriented programming section. The application provides the following technical scheme:
in a first aspect, a database transaction management method is provided, including: acquiring a current thread; the current thread is used for executing at least one database transaction; acquiring a thread local variable corresponding to the current thread; the thread local variable comprises a database parameter corresponding to the at least one database transaction; determining a database connection in the thread local variable; acquiring a transaction identifier; setting the affair of the database corresponding to the database connection as an open state under the condition that the affair identification is a preset identification; traversing the database connection and executing the at least one database transaction.
Optionally, the determining a database connection in the thread local variable includes: acquiring a global unique identifier of a database corresponding to the at least one database transaction; and determining the database connection in the thread local variable based on the global unique identifier.
Optionally, the determining a database connection in the thread local variable includes: under the condition that the connection of a database in the thread local variable is not determined, acquiring a database parameter in the thread local variable; generating database connection corresponding to the database parameters based on the database parameters; and connecting and storing the database corresponding to the database parameters to the thread local variable.
Optionally, after the connecting and storing the database corresponding to the database parameter to the thread local variable, the method further includes: and opening the affair of the database connected with the corresponding database.
Optionally, under the condition that the transaction identifier is not a preset identifier, setting the transaction of the database corresponding to the database connection to be in a closed state.
Optionally, traversing the database connection, after executing the at least one database transaction, further includes: and traversing the database connection and submitting the at least one database transaction under the condition that the transaction is successfully executed.
Optionally, traversing the database connection corresponding to the current thread, after executing the transaction, further includes: and traversing the database connection and rolling back the at least one database transaction under the condition that the transaction execution fails.
In a second aspect, there is provided a database transaction management apparatus, the apparatus comprising:
the first acquisition module is used for acquiring a current thread; the current thread comprises at least one database transaction;
the second obtaining module is used for obtaining the thread local variable corresponding to the current thread; the thread local variable comprises a database parameter corresponding to the at least one database transaction;
the connection determining module is used for determining the database connection in the thread local variable;
the third acquisition module is used for acquiring the transaction identifier;
the transaction setting module is used for setting the transaction of the database connected with the corresponding database to be in an open state under the condition that the transaction identifier is a preset identifier;
and the transaction execution module is used for traversing the database connection and executing the database transaction.
In a third aspect, an electronic device is provided, which includes a memory, a controller, and a computer program stored on the memory and operable on the controller, and the controller implements the steps of the database transaction management method when executing the computer program.
In a fourth aspect, a computer-readable storage medium is provided, in which a program is stored, and the program is used for implementing the database transaction management method provided in the first aspect when executed by a processor.
The beneficial effects of this application include at least: acquiring a current thread; the current thread is used for executing at least one database transaction; acquiring a thread local variable corresponding to a current thread; the thread local variable comprises at least one database parameter corresponding to the database transaction; determining database connections in thread local variables; acquiring a transaction identifier; setting the affair of the database connected with the corresponding database as an open state under the condition of determining that the affair identifier is a preset identifier; the database connection is traversed and at least one database transaction is executed. The problem that configuration transaction management is inconvenient due to the fact that a configuration file is set in a complex process and codes are required to be modified frequently when transactions of a database are managed in a cut-in mode of a section-oriented programming section can be solved; the database parameters corresponding to the database related to the current thread are stored through the thread local variables, whether the connection of the configuration database exists in the thread local variables is determined, if not, the database connection is set and cached in the thread local, the obtained database connection is traversed, the operation of submitting or rolling back the database transaction is completed, the unified management and operation of the database transaction are realized, the transaction of the database is managed without a mode of programming the cut-in of the cut-plane facing the cut-plane, and the convenience of database transaction management can be improved.
Drawings
In order to more clearly illustrate the detailed description of the present application or the technical solutions in the prior art, the drawings needed to be used in the detailed description of the present application or the technical solutions in the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of a method for database transaction management provided by an embodiment of the present application;
FIG. 2 is a flow chart of a database transaction management method according to another embodiment of the present application;
FIG. 3 is a block diagram of a database transaction management apparatus provided by an embodiment of the present application;
fig. 4 is a block diagram of an electronic device provided by an embodiment of the application.
Detailed Description
The technical solutions of the present application will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are only some embodiments of the present application, but not all embodiments. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
In this application, where the contrary is not intended, directional words such as "upper, lower, top and bottom" are generally used with respect to the orientation shown in the drawings, or with respect to the component itself in the vertical, vertical or gravitational direction; likewise, for ease of understanding and description, "inner and outer" refer to the inner and outer relative to the profile of the components themselves, but the above directional words are not intended to limit the application.
The following describes the database transaction management method provided by the present application in detail.
As shown in fig. 1, an embodiment of the present application provides a database transaction management method, where implementation of the method may rely on a computer program, and the computer program may be run on a computer device such as a smart phone, a tablet computer, a personal computer, or may be run on a server, and this embodiment does not limit an operation subject of the method. The method at least comprises the following steps:
In this embodiment, the current thread is used to execute at least one database transaction.
And 102, acquiring a thread local variable corresponding to the current thread.
In this embodiment, the thread local variable includes at least one database parameter corresponding to the database transaction.
In actual implementation, the database transaction executed by the current thread may involve one or more databases, and in this case, the thread local variable includes database parameters corresponding to the one or more databases.
The database parameters include, but are not limited to, database objects and database connections, and the selection of the database parameters is not limited in this embodiment.
Before determining that data in the thread local variable is connected, a global unique identifier of a database related to the current thread is acquired, and whether all database connections required by the current thread exist in the thread local variable is determined through the global unique identifier.
The global unique identifier is an identifier used for uniquely indicating the database, and different databases correspond to different global unique identifiers.
In this embodiment, the thread local variable stores a global unique identifier of a database corresponding to an existing database connection in advance. And determining the database connection required by at least one database transaction by acquiring the global unique identifier of the database corresponding to at least one database transaction and matching the global unique identifier with the global unique identifier pre-stored in the thread local variable.
Specifically, determining database connections in thread local variables includes: acquiring a global unique identifier of a database corresponding to at least one database transaction; based on the globally unique identification, a database connection in the thread local variable is determined.
In actual implementation, there is a case that there is no database connection in the thread local variable, or when the current thread relates to multiple databases, the thread local variable only includes a database connection of one or part of the multiple databases, and at this time, it is also necessary to create a database connection required by the current thread and cache the database connection in the thread local variable.
Specifically, determining database connections in thread local variables includes: under the condition that the database connection in the thread local variable is not determined, acquiring a database parameter in the thread local variable; generating database connections corresponding to the database parameters based on the database parameters; and connecting and storing the database corresponding to the database parameters to the thread local variable.
In addition, after the database corresponding to the database parameter is stored in the thread local variable in a connected manner, the method further comprises the following steps: and opening the affair of the database connected with the corresponding database.
The transaction identifier is used for determining the transaction state of the database corresponding to the database connection when the database connection is acquired.
Such as: when the value of the transaction identifier is 0, setting the transaction state of the database corresponding to the database connection as a closed state; and when the transaction identifier value is 1, setting the transaction state of the database corresponding to the database connection as an open state.
In practical implementation, the value of the transaction identifier may also be other numbers or letters, such as a, a1, and the implementation manner of the transaction identifier is not limited in this embodiment.
And 105, setting the affair of the database connected with the corresponding database to be in an open state under the condition that the affair identifier is the preset identifier.
The preset identifier is a preset identifier, is determined based on the transaction identifier, and is used for indicating that the transaction of the database corresponding to the database connection is set to be in an open state. For example: when the transaction identifier is 1, determining that the database transaction is in an open state, and setting the value of the preset identifier to be 1.
In another example, the transaction identifier is an identifier indicating that the database transaction is in a closed state, that is, in a case that the transaction identifier is not a preset identifier, the transaction connecting the corresponding database to the database is set in the closed state. At this time, the database transaction operation performed through the database connection does not need to be submitted, the database transaction is put in storage by default, and after the execution of the database transaction is completed, the transaction of the database also needs to be set to be in an open state.
In this embodiment, the following two cases are included after the execution of at least one database transaction:
first, at least one database transaction is successfully executed, and at this time, at least one database transaction needs to be submitted to complete the database operation.
Specifically, traversing the database connection, after executing at least one database transaction, further comprises: and traversing the database connection and submitting at least one database transaction under the condition that the transaction is successfully executed.
Second, at least one database transaction fails to execute, and at this time, at least one database transaction needs to be rolled back.
Specifically, traversing the database connection corresponding to the current thread, after executing the transaction, the method further includes: and traversing the database connection and rolling back at least one database transaction under the condition that the transaction execution fails.
In practical implementation, after completing the database operation of at least one database transaction, the database connection needs to be closed, including: and traversing the database connections and closing the database connections one by one.
In summary, the database transaction management method provided in this embodiment obtains the current thread; the current thread is used for executing at least one database transaction; acquiring a thread local variable corresponding to a current thread; the thread local variable comprises at least one database parameter corresponding to the database transaction; determining database connections in thread local variables; acquiring a transaction identifier; setting the affair of the database connected with the corresponding database as an open state under the condition of determining that the affair identifier is a preset identifier; the database connection is traversed and at least one database transaction is executed. The problem that configuration transaction management is inconvenient due to the fact that a configuration file is set in a complex process and codes are required to be modified frequently when transactions of a database are managed in a cut-in mode of a section-oriented programming section can be solved; the database parameters corresponding to the database related to the current thread are stored through the thread local variables, whether the connection of the configuration database exists in the thread local variables is determined, if not, the database connection is set and cached in the thread local, the obtained database connection is traversed, the operation of submitting or rolling back the database transaction is completed, the unified management and operation of the database transaction are realized, the transaction of the database is managed without a mode of programming the cut-in of the cut-plane facing the cut-plane, and the convenience of database transaction management can be improved.
In order to more clearly understand the database transaction management method provided in the present application, the present embodiment describes the method as an example, and with reference to fig. 2, the method at least includes the following steps:
In summary, the database parameters corresponding to the database related to the current thread are stored through the thread local variables, whether the connection of the configuration database exists in the thread local variables is determined, if not, the database connection is set and cached in the thread local, the obtained database connection is traversed, the operation of submitting or rolling back the database transaction is completed, and the unified management and operation of the database transaction can be realized.
The present embodiment provides a database transaction management apparatus, as shown in fig. 3, the apparatus includes at least the following modules: a first obtaining module 310, a second obtaining module 320, a connection determining module 330, a third obtaining module 340, a transaction setting module 350, and a transaction executing module 360.
A first obtaining module 310, configured to obtain a current thread; the current thread is used for executing at least one database transaction;
a second obtaining module 320, configured to obtain a thread local variable corresponding to a current thread; the thread local variable comprises at least one database parameter corresponding to the database transaction;
a connection determination module 330, configured to determine a database connection in the thread local variable;
a third obtaining module 340, configured to obtain the transaction identifier;
the transaction setting module 350 is configured to set a transaction of the database connected to the corresponding database to be in an open state when the transaction identifier is the preset identifier;
and the transaction execution module 360 is used for traversing the database connection and executing the database transaction.
For further details, reference is made to the above-described method and system embodiments.
It should be noted that: in the database transaction management apparatus provided in the above embodiment, when performing database transaction management, only the division of the above functional modules is taken as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the database transaction management apparatus is divided into different functional modules to complete all or part of the above described functions. In addition, the database transaction management apparatus and the database transaction management method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.
The present embodiment provides an electronic device as shown in fig. 4. The electronic device comprises at least a processor 401 and a memory 402.
Processor 401 may include one or more processing cores such as: 4 core processors, 8 core processors, etc. The processor 401 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 401 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 401 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 401 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 402 may include one or more computer-readable storage media, which may be non-transitory. Memory 402 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 402 is used to store at least one instruction for execution by processor 401 to implement the database transaction management methods provided by method embodiments herein.
In some embodiments, the electronic device may further include: a peripheral interface and at least one peripheral. The processor 401, memory 402 and peripheral interface may be connected by bus or signal lines. Each peripheral may be connected to the peripheral interface via a bus, signal line, or circuit board. Illustratively, peripheral devices include, but are not limited to: radio frequency circuit, touch display screen, audio circuit, power supply, etc.
Of course, the electronic device may include fewer or more components, which is not limited by the embodiment.
Optionally, the present application further provides a computer-readable storage medium, in which a program is stored, and the program is loaded and executed by a processor to implement the database transaction management method of the foregoing method embodiment.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
It is to be understood that the above-described embodiments are only a few, but not all, of the embodiments described herein. Based on the embodiments in the present application, a person skilled in the art may make other variations or changes without creative efforts, and all of them should fall into the protection scope of the present application.
Claims (10)
1. A database transaction management method, the method comprising:
acquiring a current thread; the current thread is used for executing at least one database transaction;
acquiring a thread local variable corresponding to the current thread; the thread local variable comprises a database parameter corresponding to the at least one database transaction;
determining a database connection in the thread local variable;
acquiring a transaction identifier;
setting the affair of the database corresponding to the database connection to be in an open state under the condition that the affair identification is a preset identification;
traversing the database connection and executing the at least one database transaction.
2. The method of claim 1, wherein determining the database connections in the thread local variables comprises:
acquiring a global unique identifier of a database corresponding to the at least one database transaction;
determining a database connection in the thread local variable based on the globally unique identifier.
3. The method of claim 2, wherein determining the database connections in the thread local variables comprises:
under the condition that the connection of a database in the thread local variable is not determined, acquiring a database parameter in the thread local variable;
generating a database connection corresponding to the database parameter based on the database parameter;
and connecting and storing the database corresponding to the database parameters to the thread local variable.
4. The method according to claim 3, wherein after storing the database link corresponding to the database parameter to the thread local variable, further comprising:
and opening the affair of the database connected with the corresponding database.
5. The method according to claim 1, wherein the transaction of the database connected to the corresponding database is set to a closed state if the transaction identifier is not a preset identifier.
6. The method of claim 1, wherein traversing the database connection, after performing the at least one database transaction, further comprises:
and traversing the database connection object and submitting the at least one database transaction under the condition that the transaction is successfully executed.
7. The method of claim 1, wherein traversing the database connection corresponding to the current thread further comprises, after executing the transaction:
and traversing the database connection and rolling back the at least one database transaction under the condition that the transaction execution fails.
8. A database transaction management apparatus, the apparatus comprising:
the first acquisition module is used for acquiring a current thread; the current thread is used for executing at least one database transaction;
the second obtaining module is used for obtaining the thread local variable corresponding to the current thread; the thread local variable comprises a database parameter corresponding to the at least one database transaction;
the connection determining module is used for determining the database connection in the thread local variable;
the third acquisition module is used for acquiring the transaction identifier;
the transaction setting module is used for setting the transaction of the database connected with the corresponding database to be in an open state under the condition that the transaction identifier is a preset identifier;
and the transaction execution module is used for traversing the database connection and executing the database transaction.
9. An electronic device, characterized in that the device comprises a manager and a memory; the memory stores therein a program that is loaded and executed by the manager to implement the database transaction management method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the storage medium has stored therein a program for implementing the database transaction management method according to any one of claims 1 to 7 when executed by a manager.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210111258.3A CN114490769A (en) | 2022-01-28 | 2022-01-28 | Database transaction management method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210111258.3A CN114490769A (en) | 2022-01-28 | 2022-01-28 | Database transaction management method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114490769A true CN114490769A (en) | 2022-05-13 |
Family
ID=81479324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210111258.3A Pending CN114490769A (en) | 2022-01-28 | 2022-01-28 | Database transaction management method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114490769A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106033562A (en) * | 2015-03-16 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Transaction processing method, transaction participation node and transaction coordination node |
| CN111580938A (en) * | 2020-03-27 | 2020-08-25 | 山东浪潮通软信息科技有限公司 | Transaction processing method, device, equipment and medium for work unit |
| CN112817799A (en) * | 2021-01-13 | 2021-05-18 | 中国建设银行股份有限公司 | Method and device for accessing multiple data sources based on Spring framework |
| US11080086B1 (en) * | 2019-03-12 | 2021-08-03 | Pivotal Software, Inc. | Reactive transaction management |
| CN113296897A (en) * | 2020-07-21 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method, device, equipment and machine readable medium |
-
2022
- 2022-01-28 CN CN202210111258.3A patent/CN114490769A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106033562A (en) * | 2015-03-16 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Transaction processing method, transaction participation node and transaction coordination node |
| US11080086B1 (en) * | 2019-03-12 | 2021-08-03 | Pivotal Software, Inc. | Reactive transaction management |
| CN111580938A (en) * | 2020-03-27 | 2020-08-25 | 山东浪潮通软信息科技有限公司 | Transaction processing method, device, equipment and medium for work unit |
| CN113296897A (en) * | 2020-07-21 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method, device, equipment and machine readable medium |
| CN112817799A (en) * | 2021-01-13 | 2021-05-18 | 中国建设银行股份有限公司 | Method and device for accessing multiple data sources based on Spring framework |
Non-Patent Citations (1)
| Title |
|---|
| DEMONS: "ThreadLocal详解，附带实例（threadlocal实现银行转账事务管理）", Retrieved from the Internet <URL:https://blog.csdn.net/a754895/article/details/82747807> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103207797B (en) | Capsule type customized updating method based on universal extensible firmware interface firmware system | |
| TW201942766A (en) | Device model identification method and apparatus, and processing device | |
| CN110688172B (en) | Device function mutual exclusion logic configuration method and device, electronic device and storage medium | |
| US11036797B2 (en) | Efficient storage and utilization of a hierarchical data set | |
| CN111459671A (en) | Data processing method and device, data exchange server and storage medium | |
| CN112667403B (en) | Scheduling method and device of server and electronic equipment | |
| US20240061599A1 (en) | Method and system for processing file read-write service, device, and medium | |
| WO2019047142A1 (en) | Method for program patching, device, micro control unit, and terminal device | |
| CN115392501A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN109241351A (en) | A kind of multi-source heterogeneous data preparation method of board production | |
| CN114490769A (en) | Database transaction management method, device, equipment and storage medium | |
| CN115484187B (en) | Method, equipment and storage medium for testing container network interface in container environment | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN115510064A (en) | ES alarm data backfilling method, device, equipment and medium | |
| CN111813988B (en) | HNSW node deletion method, system, device and medium for image feature library | |
| CN114186976A (en) | Workflow transfer method and device, computer equipment and storage medium | |
| US11947877B2 (en) | Anti-constraint configuration and enforcement for computer-aided design (CAD) models | |
| CN112988706A (en) | Data management method and device and electronic controller | |
| CN116595578B (en) | Power network self-checking attack and defense safety data system | |
| CN113342413B (en) | Method, apparatus, device, medium, and article for processing components | |
| US20230100758A1 (en) | Unique identifier creation and management for elaborated platform | |
| CN113867975B (en) | Quick response method and device for command line and computer equipment | |
| CN112948206B (en) | Time sequence log management system based on cloud computing and electronic equipment comprising same | |
| US20240289393A1 (en) | In-situ data processing in overlay systems using micro-overlays | |
| CN116522889A (en) | Method, device, system and medium for managing fault library of chaotic engineering platform |
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 |