CN114504828B - Method and system for realizing memory consistency by data rollback - Google Patents
Method and system for realizing memory consistency by data rollback Download PDFInfo
- Publication number
- CN114504828B CN114504828B CN202210150030.5A CN202210150030A CN114504828B CN 114504828 B CN114504828 B CN 114504828B CN 202210150030 A CN202210150030 A CN 202210150030A CN 114504828 B CN114504828 B CN 114504828B
- Authority
- CN
- China
- Prior art keywords
- value
- updated
- data
- service data
- original
- 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.)
- Active
Links
Images
Classifications
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/70—Game security or game management aspects
- A63F13/77—Game security or game management aspects involving data related to game devices or game servers, e.g. configuration data, software version or amount of memory
-
- 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/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Computing Systems (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method and a system for realizing memory consistency by data rollback, comprising the following steps: acquiring an original value of service data, and setting an update value and a copy value; the updated value and the copy value are initially set as original values; when the service data is updated, writing the result after the service data is changed into the updated value; when service data is submitted, synchronizing the updated value to the original value; and synchronizing the copy value to the original value when the business is abnormal and the business data rolls back. The scheme of the invention has finer granularity, only the variable data is submitted and rolled back, the relative performance is higher, the memory consistency problem caused by logic abnormality in common business development is solved, and the developer is greatly convenient to concentrate main efforts on specific business development logics rather than the problem of processing abnormality and related memory data consistency caused by abnormality.
Description
Technical Field
The present invention relates to the field of network communications technologies, and in particular, to a method and system for implementing memory consistency by data rollback.
Background
With the rapid popularization of smart phones and the rapid development of networks, related services of the mobile internet have gradually become the focus of attention of various manufacturers in China. From the whole industry perspective, the China mobile game industry is in a rapid development stage. In recent years, the mobile game industry in China has gained rapid development under the combined promotion of telecom operators and mobile game developers. With the development of interactive entertainment technology, various types of interactive game applications have been greatly developed, and various game types and game control modes exist, and the game forms are also excessive from the aspects of computer or game machine to mobile phone games.
Conventional game servers consider performance reasons in that data is in real-time operating memory, rather than in a real-time operating database. Typically, a game client requests it to cause memory data for a plurality of modules to change. When processing the game service logic, if the exception is thrown in the middle, the problem of memory data consistency can occur.
Taking the logic of a player purchasing props with a diamond to a store as an example, there are two implementations of pseudocode for game logic:
first kind of// first kind
costDiamond ()// diamond button
sometangelse ()// other logic, such as log
addItem ()// add prop
Second kind of//
addItem ()// add prop
sometangelse ()// other logic, such as log
costDiamond ()// diamond button
For the first implementation, the fastening is followed by the adding. If an intermediate code (e.g., sometangense) throws an anomaly, this may result in the player's diamond being buckled, but no prop is added to the player. This is unfair to the player. This is typically followed by manual log-based compensation of the player's prop.
For the second implementation, add-then-snap. If an intermediate code (e.g., sometangense) throws an anomaly, it will appear that the prop is added, but the diamond is not deducted. This is unfair to the game operators. And in the case of multiple times, the game operation accident that the player continuously brushes the prop can occur.
In any implementation manner, when the memory data is inconsistent, a certain influence is generated on the game.
Conventional internet or APP servers, typically, operate databases directly on the data changes, and when errors are found, rollback operations can be performed directly. Data change modifications of game servers are mostly direct modifications to memory due to performance considerations. A consistency solution for memory data is required and conventional database solutions are not suitable.
Disclosure of Invention
The invention provides a method and a system for realizing memory consistency by data rollback, which solve the game experience problem caused by common memory consistency in the prior art.
According to one aspect of the present invention, there is provided a method for implementing memory consistency by data rollback, including:
acquiring an original value of service data, and setting an update value and a copy value; the updated value and the copy value are initially set as original values;
when the service data is updated, writing the result after the service data is changed into the updated value;
when service data is submitted, synchronizing the updated value to the original value;
and synchronizing the copy value to the original value when the business is abnormal and the business data rolls back.
When the service data is updated, writing the result after the service data is changed into the updated value, which comprises the following steps:
and when the business is updated, writing the updated business data into an updated value.
The method further comprises the steps of:
and when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
And synchronizing the updated value to the original value when the service data is submitted, comprising:
and when the service data updating and submitting processes are not abnormal, synchronizing the updating value to the original value to complete the service data updating process.
And synchronizing the updated value to the original value when the service data is submitted, comprising:
and when the service data submission is abnormal, rolling back the service data, and synchronizing the copy value to the original value.
The method further comprises the steps of:
when the updated value is abnormal, the original value is not affected.
According to another aspect of the present invention, there is provided a system for implementing memory consistency by data rollback, the system comprising:
the original value acquisition unit is used for acquiring the original value of the service data;
an update value setting unit configured to set an update value; the updated value is initially set as an original value;
a copy value setting unit configured to set a copy value; the copy value is initially set as an original value;
the updating unit is used for writing the result after the service data change into the updating value when the service data is updated;
the submitting unit is used for synchronizing the updated value to the original value when service data is submitted;
and the rollback unit is used for synchronizing the copy value to the original value when the business data rollback occurs in abnormal business.
The submitting unit is specifically configured to:
and when the service data updating and submitting processes are not abnormal, synchronizing the updating value to the original value to complete the service data updating process.
The rollback unit is specifically configured to:
and when the service data submission is abnormal, rolling back the service data, and synchronizing the copy value to the original value.
The updating unit is specifically configured to:
when the business is updated, the updated business data is written into an updated value;
and when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
The beneficial effects of adopting above-mentioned scheme are:
acquiring an original value of service data, and setting an update value and a copy value; the updated value and the copy value are initially set as original values; when the service data is updated, writing the result after the service data is changed into the updated value; when service data is submitted, synchronizing the updated value to the original value; and synchronizing the copy value to the original value when the business is abnormal and the business data rolls back. The scheme of the invention has finer granularity, only the variable data is submitted and rolled back, the relative performance is higher, the memory consistency problem caused by logic abnormality in common business development is solved, and the developer is greatly convenient to concentrate main efforts on specific business development logics rather than the problem of processing abnormality and related memory data consistency caused by abnormality.
Drawings
Fig. 1 is a schematic flow chart of a data rollback method according to an embodiment of the present invention.
Fig. 2 is a schematic flow chart of a method for implementing memory consistency by data rollback according to an embodiment of the present invention.
Fig. 3 is a schematic flow chart of a method for implementing data rollback according to an embodiment of the present invention.
Fig. 4 is a schematic diagram of a system structure for implementing memory consistency by data rollback according to an embodiment of the present invention.
Detailed Description
The principles and features of the present invention are described below with reference to the drawings, the examples are illustrated for the purpose of illustrating the invention and are not to be construed as limiting the scope of the invention. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments may be combined with each other.
A typical business logic exception refers to a business logic code or related code throwing an exception, such as a null pointer or the like. When abnormal business logic occurs, as mentioned in the background art, the problem of inconsistent memory data occurs, so that a certain influence (player side or game operation side) is generated on the game. In order to solve the problem of memory data consistency caused by business logic abnormality, the embodiment of the invention provides the following solutions.
With the rollback data structure, memory data changes do not directly update the original value. And after the business logic is executed, uniformly submitting the change data. When the commit is abnormal, the copy value is used to roll back directly. The scheme is suitable for business logic with relatively low granularity and relatively sensitive performance.
As shown in fig. 1, the primary service logic may cause corresponding sub-service related module data to change. Then the memory data is defined within the corresponding sub-service logic module by a rollback data structure. When the sub-module business memory data changes, the original value is not directly updated, but the updated value is changed. And after the business logic is executed, uniformly submitting all sub-module change values. If the commit is abnormal, the copy values are used in turn to roll back.
The invention is further described below with reference to the accompanying drawings.
As shown in fig. 2, a schematic flow chart of a method for implementing memory consistency by data rollback provided in embodiment 1 of the present invention is specifically as follows:
In the embodiment of the invention, the rollback data structure is used, and the memory data change does not directly update the original value. And after the business logic is executed, uniformly submitting the change data. When the commit is abnormal, the copy value is used to roll back directly.
In the embodiment of the invention, a rollback data structure interface is defined, and three methods are arranged inside:
the preparation is used for initializing data before the business logic is executed;
the commit is used for submitting all data changes after the business execution is finished;
the rollback is used to roll back data when commit data changes fail.
Rollback data structure implementation (original, updated, duplicate):
initializing: the updated value is set as the original value, and the duplicate value is set as the original value;
when the data is updated, the original value is not directly updated, but the updated value is directly changed;
when the real submission is performed, synchronizing the updated value to the original value;
at rollback, the duplicate value is synchronized to the original value.
And step 12, when the service data is updated, writing the result after the service data is changed into the updated value.
In the embodiment of the invention, the business is changed without abnormality, and when the business data is updated, the updated business data is written into the updated value.
And when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
And step 13, synchronizing the updated value to the original value when service data is submitted.
In the embodiment of the invention, when the service data updating and submitting processes are not abnormal, the updating value is synchronized to the original value, and the service data updating process is completed.
In the embodiment of the invention, when the service data submission is abnormal, the service data rollback is performed, and the copy value is synchronized to the original value.
And 14, synchronizing the copy value to the original value when the business is abnormal and the business data rolls back.
In the embodiment of the invention, service data rollback is needed to synchronize the copy value to the original value when the service data is submitted or the update value is updated or the update value is synchronized to the original value.
Illustrated in two rollback data structures RInt and RList.
Pseudo code implementation of RInt:
pseudo code implementation of RList:
the pseudo code is rewritten as follows, with the examples mentioned in the background:
if an exception is thrown at sometangelse, there is no concern that the actual original value is not changed here, but only the changed updated value, which has not yet been committed. After all the related data are changed, all the related changes are submitted together. If a commit is incorrect, such as a success or a failure, an inconsistency occurs. The rollback operation is performed at this time, solving the consistency problem.
In one embodiment of the invention, as shown in FIG. 3, the data structure is set to an original value, an updated value, a duplicate value. During initialization, the update value and the copy value are set as original values. When the data is changed and updated, the change directly changes the updated value. And synchronizing the updated value to the original value during the normal submitted process, so as to realize the change of the original value and complete the data updating.
If any anomalies occur during this process, a data rollback is performed, synchronized to the original value with no branching. Since the copy value is not changed at this time, the content thereof is still the content of the original value (and the content of the original value may have been synchronized to the content of the updated value at this time). The original value is updated with the contents of the duplicate value in order to rollback the contents of the original value to the original contents so that the original value remains unchanged when an abnormality occurs in the data.
The scheme has finer granularity, only variable data is submitted and rolled back, and the relative performance is higher. The method is suitable for service scenes, has higher requirements on relative performance, and is relatively complex to use for service developers.
In the embodiment of the invention, a plurality of R-type rollback basic data structures are realized, wherein the basic data structures comprise an original value, an updated value and a copy value. And simultaneously setting the updated value and the copy value as original values during initialization. When the data is changed, the original value is not directly updated, but is directly changed to the updated value. At this time, if an exception occurs, no memory consistency problem occurs because the original value is not modified. And after all data are changed, uniformly submitting and synchronizing the updated value to the original value. If abnormality occurs in the submitting process, the copy value is synchronized with the original value, and the problem of memory consistency does not occur.
As shown in fig. 4, a system for implementing memory consistency by data rollback according to an embodiment of the present invention is provided, where,
a primary value obtaining unit 21, configured to obtain a primary value of service data;
an update value setting unit 22 for setting an update value; the updated value is initially set as an original value;
a copy value setting unit 23 for setting a copy value; the copy value is initially set as an original value;
an updating unit 24, configured to write the result after the service data change into the updated value when the service data is updated;
a submitting unit 25, configured to synchronize the updated value to the original value when service data is submitted;
and the rollback unit 26 is configured to synchronize the duplicate value to the original value when the traffic is abnormal and the traffic data is rolled back.
The submitting unit 25 is specifically configured to:
and when the service data updating and submitting processes are not abnormal, synchronizing the updating value to the original value to complete the service data updating process.
The rollback unit 26 is specifically configured to:
and when the service data submission is abnormal, rolling back the service data, and synchronizing the copy value to the original value.
The updating unit 24 is specifically configured to:
when the business is updated, the updated business data is written into an updated value;
and when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
In the embodiment of the invention, the original value of the service data is obtained, and the update value and the copy value are set; the updated value and the copy value are initially set as original values; when the service data is updated, writing the result after the service data is changed into the updated value; when service data is submitted, synchronizing the updated value to the original value; and synchronizing the copy value to the original value when the business is abnormal and the business data rolls back. The scheme of the invention has finer granularity, only the variable data is submitted and rolled back, the relative performance is higher, the memory consistency problem caused by logic abnormality in common business development is solved, and the developer is greatly convenient to concentrate main efforts on specific business development logics rather than the problem of processing abnormality and related memory data consistency caused by abnormality.
The present invention has been described in detail with reference to specific embodiments, but the above embodiments are merely examples, and the present invention is not limited to the above embodiments.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (8)
1. A method for implementing memory consistency by data rollback, the method comprising:
acquiring an original value of service data, and setting an update value and a copy value; the updated value and the copy value are initially set as original values;
when the service data is updated, writing the result after the service data is changed into the updated value;
when service data is submitted, synchronizing the updated value to the original value; the method specifically comprises the following steps: when the business data updating and submitting processes are not abnormal, synchronizing the updating value to the original value to finish the business data updating process;
and synchronizing the copy value to the original value when the business is abnormal and the business data rolls back.
2. The method of claim 1, wherein writing the updated value with the changed service data comprises:
and when the business is updated, writing the updated business data into an updated value.
3. The method of claim 2, wherein the method further comprises:
and when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
4. The method of claim 1, wherein synchronizing the replica value to the original value when the traffic is abnormal and traffic data rolls back comprises:
and when the service data submission is abnormal, rolling back the service data, and synchronizing the copy value to the original value.
5. The method of claim 1, wherein the method further comprises:
when the updated value is abnormal, the original value is not affected.
6. A system for implementing memory consistency by data rollback, the system comprising:
the original value acquisition unit is used for acquiring the original value of the service data;
an update value setting unit configured to set an update value; the updated value is initially set as an original value;
a copy value setting unit configured to set a copy value; the copy value is initially set as an original value;
the updating unit is used for writing the result after the service data change into the updating value when the service data is updated; the method specifically comprises the following steps: when the business data updating and submitting processes are not abnormal, synchronizing the updating value to the original value to finish the business data updating process;
the submitting unit is used for synchronizing the updated value to the original value when service data is submitted;
and the rollback unit is used for synchronizing the copy value to the original value when the business data rollback occurs in abnormal business.
7. The system of claim 6, wherein the rollback unit is specifically configured to:
and when the service data submission is abnormal, rolling back the service data, and synchronizing the copy value to the original value.
8. The system according to claim 6, wherein the updating unit is specifically configured to:
when the business is updated, the updated business data is written into an updated value;
and when the service is abnormally changed and the service data is abnormally updated, the updated value is not changed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210150030.5A CN114504828B (en) | 2022-02-08 | 2022-02-08 | Method and system for realizing memory consistency by data rollback |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210150030.5A CN114504828B (en) | 2022-02-08 | 2022-02-08 | Method and system for realizing memory consistency by data rollback |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114504828A CN114504828A (en) | 2022-05-17 |
| CN114504828B true CN114504828B (en) | 2023-04-28 |
Family
ID=81550820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210150030.5A Active CN114504828B (en) | 2022-02-08 | 2022-02-08 | Method and system for realizing memory consistency by data rollback |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114504828B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015184925A1 (en) * | 2014-10-24 | 2015-12-10 | 中兴通讯股份有限公司 | Data processing method for distributed file system and distributed file system |
| CN108123967A (en) * | 2016-11-28 | 2018-06-05 | 中国石油天然气股份有限公司 | The method of data synchronization and system of a kind of group system |
| CN109603149A (en) * | 2018-12-12 | 2019-04-12 | 北京像素软件科技股份有限公司 | Method of data synchronization and device |
| CN110585698A (en) * | 2019-09-29 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Virtual asset transaction method and related device |
| CN113268540A (en) * | 2021-03-26 | 2021-08-17 | 北京视博云信息技术有限公司 | Data synchronization method and device |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102081665A (en) * | 2008-12-10 | 2011-06-01 | 阿里巴巴集团控股有限公司 | Data synchronization method and device |
| US8600944B2 (en) * | 2010-09-24 | 2013-12-03 | Hitachi Data Systems Corporation | System and method for managing integrity in a distributed database |
| CN109241175B (en) * | 2018-06-28 | 2021-06-04 | 东软集团股份有限公司 | Data synchronization method and device, storage medium and electronic equipment |
| CN110032428B (en) * | 2019-02-21 | 2023-06-27 | 创新先进技术有限公司 | Method and device for executing distributed transaction |
| CN111046109B (en) * | 2019-12-27 | 2023-09-15 | 深圳市迅雷网络技术有限公司 | Cross-chain task processing method, device, equipment and readable storage medium |
| CN112600830B (en) * | 2020-12-07 | 2024-03-26 | 腾讯科技（深圳）有限公司 | Service data processing method and device, electronic equipment and storage medium |
| CN113836155A (en) * | 2021-09-14 | 2021-12-24 | 青岛海尔科技有限公司 | Data processing method and device based on distributed system and storage medium |
-
2022
- 2022-02-08 CN CN202210150030.5A patent/CN114504828B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015184925A1 (en) * | 2014-10-24 | 2015-12-10 | 中兴通讯股份有限公司 | Data processing method for distributed file system and distributed file system |
| CN108123967A (en) * | 2016-11-28 | 2018-06-05 | 中国石油天然气股份有限公司 | The method of data synchronization and system of a kind of group system |
| CN109603149A (en) * | 2018-12-12 | 2019-04-12 | 北京像素软件科技股份有限公司 | Method of data synchronization and device |
| CN110585698A (en) * | 2019-09-29 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Virtual asset transaction method and related device |
| CN113268540A (en) * | 2021-03-26 | 2021-08-17 | 北京视博云信息技术有限公司 | Data synchronization method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114504828A (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3249523B1 (en) | Zero downtime maintenance in constrained systems | |
| US10437795B2 (en) | Upgrading systems with changing constraints | |
| CN102147747B (en) | The system and method for the upgrading path strengthened | |
| US20090183145A1 (en) | Techniques for reducing down time in updating applications with metadata | |
| CN110209735B (en) | Database backup method, database backup device, computing device, and storage medium | |
| CN110990182A (en) | Transaction processing method, device, equipment and storage medium | |
| US20130151494A1 (en) | Consistent Database Recovery Across Constituent Segments | |
| CN112364049B (en) | Data synchronization script generation method, system, terminal and storage medium | |
| CN111538519A (en) | Version upgrading method and device | |
| CN110599341A (en) | Transaction calling method and system | |
| CN106033362A (en) | Method and device for processing flash memory partition | |
| DE102022129468A1 (en) | IMPLEMENTATION OF OBJECT VERSIONING AND CONSISTENCY AT SCALING | |
| CN113760234B (en) | Software development method and system | |
| CN104111843A (en) | Sandbox based script updating method and system | |
| CN105938446B (en) | The data supported based on RDMA and hardware transactional memory replicate fault-tolerance approach | |
| CN114504828B (en) | Method and system for realizing memory consistency by data rollback | |
| CN112738550B (en) | Content data processing method and device, electronic equipment and medium | |
| CN111949311B (en) | Gray level release method and system | |
| CN107465725B (en) | Heterogeneous long transaction processing system and method based on client information control system | |
| CN116466983A (en) | Code management device, method, storage medium and electronic device | |
| CN111240891A (en) | Data recovery method and device based on data consistency among multiple tables of database | |
| CN112256978B (en) | Data processing method, device and medium based on data model | |
| JP2000035911A (en) | Equalization method for data base | |
| CN114610351A (en) | Database upgrading method | |
| CN109376141A (en) | A kind of data migration method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |