CN103019826B - A kind of method and apparatus of issued transaction - Google Patents
A kind of method and apparatus of issued transaction Download PDFInfo
- Publication number
- CN103019826B CN103019826B CN201210581869.0A CN201210581869A CN103019826B CN 103019826 B CN103019826 B CN 103019826B CN 201210581869 A CN201210581869 A CN 201210581869A CN 103019826 B CN103019826 B CN 103019826B
- Authority
- CN
- China
- Prior art keywords
- transaction
- transaction information
- current
- information
- module
- 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
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000012217 deletion Methods 0.000 claims description 15
- 230000037430 deletion Effects 0.000 claims description 15
- 230000001419 dependent effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 13
- 238000003672 processing method Methods 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 2
- 238000004140 cleaning Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The method and apparatus that the embodiment of the invention discloses a kind of issued transaction, the method is specially, the transaction information of store transaction in data base in advance, during described transaction information includes that Transaction Identifier and transaction status, described transaction status are divided into and reform, do not reform and reform；Judge whether Current transaction meets preset trigger condition, if it is, the transaction information that the Transaction Identifier that obtains described Current transaction is corresponding；Described Current transaction is re-executed according to described transaction information.The present invention is no longer dependent on affairs coordinator, but by prestoring the transaction information for issued transaction so that when meeting trigger condition, the transaction information that the Transaction Identifier that can prestore with direct basis is corresponding, re-execute affairs, thus improve the efficiency of issued transaction.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a transaction processing method and device.
Background
A transaction refers to a series of operations performed as a single logical unit of work. A transaction, such as an online purchase, is a transaction, and the transaction process at least comprises the following database operations: updating the inventory information of the commodities purchased by the client; saving customer payment information, possibly including interaction with a banking system; generating an order and saving the order in a database; user related information, such as the number of purchases, etc., is updated. Normally, these operations will be performed successfully, and eventually the transaction is successful, and all database information related to the transaction is also successfully updated. However, if an error occurs in any of the series of processes, such as an abnormality in updating the inventory information of the goods, insufficient deposit on the bank account of the customer, etc., the transaction will be failed. Once the transaction fails, all information in the database must be kept unchanged before the transaction, for example, the transaction fails due to failure when the user information is updated in the last step, and it must be ensured that the failed transaction does not affect the state of the database, that is, the stock information is not updated, the user does not pay, and the order is not generated. Otherwise, the information of the database will be confusing and unpredictable.
In the prior art, the 2PC protocol, namely the two-phase commit protocol, is generally used for processing transactions. The 2PC protocol specifically includes:
1) the application program calls a commit method in the transaction coordinator;
2) the transaction coordinator will contact each resource manager involved in the transaction and inform them that the transaction is ready to commit;
3) in order to respond to the prepare phase in a positive way, the resource manager must put itself in the following state: ensuring that a transaction can be committed when required to commit the transaction or rolled back when required to roll back the transaction. Most resource managers will write a diary file (or equivalent) containing their scheduled changes to the persistent storage. If the resource manager is unable to prepare the transaction, it responds back to the transaction coordinator with a negative response;
4) the transaction coordinator collects all responses from the resource manager;
5) in the second phase, the transaction coordinator notifies each resource manager of the results of the transaction. If either resource manager responds negatively, the transaction coordinator will send a rollback command to all resource managers involved in the transaction. If the resource managers all respond affirmatively, the transaction coordinator will instruct all resource managers to commit the transaction. Once the resource manager is notified of the commit, the transaction cannot thereafter fail. By responding to the first phase in a positive manner, each resource manager has ensured that the transaction will not fail if it is later notified that it committed the transaction.
For the above example of online shopping transactions, the transaction is processed using the 2PC protocol, and specifically by a separate software component called a transaction coordinator, to avoid confusion of database information.
However, in the 2PC protocol, only one transaction coordinator is relied on to process a series of operations in a transaction one by one, and the problem of low transaction processing efficiency exists.
Disclosure of Invention
In order to improve the efficiency of transaction processing, the invention provides a transaction processing method and a transaction processing device.
The invention provides a transaction processing method, which comprises the following steps:
transaction information of a transaction is stored in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state, and the transaction state is divided into a redo state, a non-redo state and a redo state;
judging whether the current transaction meets a preset trigger condition, if so, acquiring transaction information corresponding to the transaction identifier of the current transaction;
and re-executing the current transaction according to the transaction information.
Preferably, the determining whether the current transaction meets a preset trigger condition includes:
presetting the transaction submission failure as the trigger condition;
and judging whether the current transaction meets the transaction submission failure or not.
Preferably, the determining whether the current transaction meets a preset trigger condition includes:
presetting any time period as a trigger cycle;
and under the condition that the time difference between the time meeting the trigger period last time and the current time is not less than the trigger period, judging whether the transaction state of the current transaction is not redo.
Preferably, the storing transaction information of the transaction in the database in advance includes:
creating a plurality of tables with equal size in the database in advance;
transaction information for the transaction is stored in the table.
Preferably, the method further comprises:
presetting a deleting condition;
and judging whether the table storing the transaction information in the database meets the deletion condition, and if so, deleting the table.
The invention also provides a transaction processing device, which comprises:
the storage module is used for storing transaction information of a transaction in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state, and the transaction state is divided into a redo state, a non-redo state and a redo state;
the first judgment module is used for judging whether the current transaction meets a preset trigger condition or not;
the first obtaining module is used for obtaining the transaction information corresponding to the transaction identifier of the current transaction when the first judging module has a positive result;
and the execution module is used for re-executing the current transaction according to the transaction information in the first acquisition module.
Preferably, the first determining module includes:
the first setting submodule is used for presetting the transaction submission failure as the trigger condition;
and the first judgment submodule is used for judging whether the current transaction meets the transaction submission failure or not.
Preferably, the first determining module includes:
the second setting submodule is used for presetting any time period as a trigger cycle;
and the second judgment submodule is used for judging whether the transaction state of the current transaction is not redo under the condition that the time difference between the moment meeting the trigger period last time and the current moment is equal to the trigger period.
Preferably, the storage module includes:
a creating submodule for creating a plurality of tables in the database in advance;
and the storage submodule is used for storing the transaction information of the transaction in the table.
Preferably, the apparatus further comprises:
the first setting module is used for presetting deletion conditions;
the second judgment module is used for judging whether a table for storing the transaction information in the database meets the deletion condition;
and the deleting module is used for deleting the table when the second judging module has a positive result.
The invention stores transaction information of a transaction in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state; secondly, acquiring transaction information corresponding to the transaction identifier of the current transaction under the condition that a trigger condition is met; and finally, redoing the current transaction according to the acquired transaction information. Compared with the prior art, the invention does not rely on a transaction coordinator any more, but stores the transaction information for transaction processing in advance, so that when the triggering condition is met, the transaction can be re-executed directly according to the transaction information corresponding to the transaction identifier stored in advance, thereby improving the efficiency of transaction processing.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a flow chart of a method for transaction processing according to a first embodiment of the present invention;
fig. 2 is a schematic diagram of a transaction information table for storing transaction information according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating one implementation of step 102 according to a first embodiment of the present invention;
FIG. 4 is a flowchart illustrating one implementation of step 102 according to a first embodiment of the present invention;
FIG. 5 is a flowchart of a transaction processing method according to a second embodiment of the present invention;
fig. 6 is a block diagram of a transaction processing apparatus according to a third embodiment of the present invention;
fig. 7 is a structural diagram of the storage module 601 according to a third embodiment of the present invention;
fig. 8 is a structural diagram of the first determining module 602 according to a third embodiment of the present invention;
fig. 9 is a structural diagram of the first determining module 602 according to a third embodiment of the present invention;
fig. 10 is a block diagram of an apparatus according to a third embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.
The first embodiment,
Referring to fig. 1, fig. 1 is a flowchart of a first embodiment of a transaction processing method provided by the present invention, where this embodiment may specifically include:
step 101, storing transaction information of a transaction in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state, and the transaction state is divided into a redo state, a non-redo state and a redo state.
In this embodiment, transaction information of a transaction is stored in the database in advance, where the transaction information includes related data when the transaction occurs, and the transaction information of the occurred transaction is stored in the database in advance, so that the subsequent step can redo the transaction according to the transaction information.
In actual operation, the database for storing the transaction may be a relational database, such as an Oracle or other relational database, and since the relational database has high stability and known reliability, the database can be used to store the transaction information of all things, so as to facilitate subsequent steps to search for relevant transaction information in the relational database, thereby redoing the transaction. The database for storing the transaction information may also be a memory database, and because the memory database is mainly used for improving the performance of data processing, the reliability of the memory database is lower than that of a relational database. The storage of the transaction information is typically performed using a relational database in this embodiment.
In this embodiment, the format for storing the transaction information may be in the form of a table, and a data structure for storing may be as shown in fig. 2. Referring to fig. 2, fig. 2 is a schematic diagram of a transaction information table for storing transaction information, and parameters in the table shown in fig. 2 are stored by using varchar2 type, which is mainly used to improve system performance when data is inserted, and simultaneously avoid performance loss caused by related operations.
In general, the transaction information parameters in the transaction information table may be stored using 5 varchar2(4000), and in this embodiment, to support the storage space expansion in special cases, 5 varchar2(4000) fields are reserved in the database.
In practical operation, the transaction information includes a transaction identifier, and the transaction identifier is used to uniquely identify the transaction information of any transaction. The transaction identification may be a sessionid field in the transaction information, and the sessionid field may be generated by a random number algorithm. The transaction identifier can also be set according to the occurrence sequence of the transactions and is used for uniquely identifying any transaction. The simultaneous transaction identification may also be determined by the sessionid field and the order of occurrence of the transaction simultaneously.
Specifically, the transaction state field in the transaction information can be divided into three states of redo, non-redo and redo, and the redo indicates that the corresponding transaction has been redone; "not redo" means that its corresponding transaction has not been redone; "redoing" means that its corresponding transaction has not been redone. Transactions with transaction status "redo" may be redone.
And 102, judging whether the current transaction meets a preset trigger condition, and if so, entering a step 103.
In this embodiment, transaction information of the transaction is stored in advance, whether the currently executed transaction meets a preset trigger condition for re-executing the transaction is determined, and if the currently executed transaction meets the trigger condition, the process proceeds to step 103.
In actual operation, the trigger condition may be preset as a transaction commit failure, that is, when a transaction commit fails, the transaction that failed to commit is redone.
In this case, referring to fig. 3, fig. 3 is one of the execution manners of step 102, and the specific execution steps are as follows:
step 301, setting the transaction commit failure as a trigger condition for triggering the transaction redo in advance.
Step 302, judging whether the current transaction meets the preset triggering condition of transaction submission failure, if so, entering step 103.
Specifically, the method for determining the transaction commit failure is the prior art, and is not described herein again, and the method for determining the transaction commit failure by using which method does not affect the implementation of this embodiment.
In actual operation, the trigger condition may also be set that the system time satisfies a preset period for scanning the transaction information, and the transaction status field in the scanned transaction information of the current transaction is not redo.
In this case, referring to fig. 4, fig. 4 is also one of the execution manners of step 102, and the specific execution steps are as follows:
step 401, presetting any time period as a trigger cycle.
Step 402, judging whether the time difference between the time meeting the trigger period last time and the current time is not less than a preset trigger period, if so, entering step 403.
Step 403, judging whether the transaction state of the current transaction is not redo, if so, entering step 103.
Specifically, the trigger period may be set according to a user requirement, and the set trigger period may be adjusted. If the trigger period is set to 5 minutes, the system will scan the database storing the transaction information every 5 minutes to find out the transaction that needs to be redone.
In actual operation, a time difference between a time meeting a trigger period last time and a current time is obtained through calculation, that is, a time interval between two adjacent database scans performed by the system is obtained, the time interval obtained through calculation is compared with a preset trigger period, and if the time interval is greater than or equal to the preset trigger period, it indicates that the system needs to scan the database.
Specifically, the transaction information includes a transaction status field, the transaction status is used to indicate the status of the transaction, and the system determines whether the transaction needs to be redone according to the status of the transaction. The transaction state is specifically divided into three states, specifically: redo, not redo, and redo. If the transaction status of the current transaction is not redo, step 103 is entered.
In this embodiment, if the current transaction does not satisfy the preset trigger condition, the current transaction is executed normally.
And 103, acquiring transaction information corresponding to the transaction identifier of the current transaction.
In this embodiment, when the current transaction meets the preset trigger condition, the database for storing the transaction information is queried according to the transaction identifier of the current transaction, and the transaction information corresponding to the transaction identifier is obtained, where the transaction information includes all data information used for redoing the transaction.
And 104, re-executing the current transaction according to the transaction information.
According to the embodiment, the current transaction is redone according to the acquired transaction information of the current transaction, namely, the current transaction is re-executed.
In this embodiment, transaction information of a transaction is stored in a database in advance, where the transaction information includes a transaction identifier and a transaction state; secondly, acquiring transaction information corresponding to the transaction identifier of the current transaction under the condition that a trigger condition is met; and finally, redoing the current transaction according to the acquired transaction information. Compared with the prior art, the invention does not rely on a transaction coordinator any more, but stores the transaction information for transaction processing in advance, so that when the triggering condition is met, the transaction can be re-executed directly according to the transaction information corresponding to the transaction identifier stored in advance, thereby improving the efficiency of transaction processing.
Example II,
Because the performance of the system may be affected when the data amount of the data storage is large, in order to reduce the performance influence of the stored transaction information on normal transaction processing and to timely recover the storage space, a strategy of timely cleaning the transaction information may be adopted.
Referring to fig. 5, fig. 5 is a flowchart of a second embodiment of a transaction processing method provided by the present invention, where this embodiment may specifically include:
step 501, creating a plurality of tables in the database in advance, and storing the transaction information of the transaction in the tables.
In this embodiment, a plurality of tables are created in advance in a database for storing transaction information, and the tables are used for storing the transaction information of the transaction.
In practice, the created tables may be equal-sized tables, and if a table is particularly large, the amount of data stored in the table is also very large, which may result in the effect of affecting the system performance.
Specifically, the transaction information stored in the table may be divided according to time, for example, in units of weeks, the transaction information of the transactions executed in the same week is stored in the same table, which is beneficial to cleaning the transaction information in the subsequent steps.
Step 502, judging whether the current transaction meets a preset trigger condition, if so, entering step 503:
step 503, acquiring transaction information corresponding to the transaction identifier of the current transaction;
and step 504, re-executing the current transaction according to the transaction information.
The steps 502-504 in this embodiment are the same as the steps 102-104 in the first embodiment, and therefore are not described herein again.
And step 505, presetting a deleting condition of the transaction information.
In this embodiment, a deletion condition for clearing the transaction information stored in the database is preset, and specifically, the deletion condition may be set to be one week, that is, the transaction information whose storage time in the database is one week is deleted, so as to recycle the storage space of the database.
Step 506, judging whether the table storing the transaction information in the database meets the deletion condition, if so, entering step 507.
In this embodiment, it is determined whether the table for storing the transaction information in the database satisfies a preset deletion condition, for example, some transaction information is stored in any table and the storage time of the transaction information reaches one week, and if the preset deletion condition is that the transaction information whose storage time is one week needs to be cleared, the system deletes the table.
And step 507, deleting the table meeting the preset deleting condition.
In this embodiment, when the table storing the transaction information in the database satisfies the preset deletion condition, the table satisfying the preset deletion condition is deleted to release the storage space.
Compared with the first embodiment, the first embodiment stores the transaction information in the form of the table in the database, so that the transaction information with longer storage time can be cleaned in time, the storage space can be recycled, and the performance of the system can be improved.
Example III,
Referring to fig. 6, fig. 6 is a device structure diagram of a third embodiment of a transaction processing device provided in the present invention, where the third embodiment may specifically include:
the storage module 601 is configured to store transaction information of a transaction in a database in advance, where the transaction information includes a transaction identifier and a transaction state, and the transaction state is divided into redo, non-redo, and redo;
referring to fig. 7, fig. 7 is a structural diagram of the storage module 601, where the storage module 601 includes:
a creating sub-module 701 for creating a plurality of tables in the database in advance;
a storage sub-module 702, configured to store transaction information of the transaction in the table.
A first determining module 602, configured to determine whether a current transaction satisfies a preset trigger condition;
referring to fig. 8, fig. 8 is a structural diagram of the first determining module 602, where the first determining module 602 may include:
the first setting sub-module 801 is configured to preset the transaction commit failure as the trigger condition;
a first determining sub-module 802, configured to determine whether the current transaction satisfies a transaction commit failure.
Referring to fig. 9, fig. 9 is a structural diagram of the first determining module 602, and the first determining module 602 may further include:
a second setting submodule 901, configured to preset any time period as a trigger cycle;
the second determining submodule 902 is configured to determine whether the transaction state of the current transaction is not redo under the condition that the time difference between the time that the trigger period is last satisfied and the current time is equal to the trigger period.
A first obtaining module 603, configured to obtain, when the result of the first breaking module is yes, transaction information corresponding to the transaction identifier of the current transaction;
an executing module 604, configured to re-execute the current transaction according to the transaction information in the first obtaining module.
Referring to fig. 10, fig. 10 is a block diagram further included in the apparatus structure diagram of the present embodiment, and specifically further includes:
a first setting module 1001 configured to preset a deletion condition;
a second judging module 1002, configured to judge whether a table storing the transaction information in the database satisfies the deletion condition;
a deleting module 1003, configured to delete the table if the result of the second determining module is yes.
In this embodiment, transaction information of a transaction is stored in a database in advance, where the transaction information includes a transaction identifier and a transaction state; secondly, acquiring transaction information corresponding to the transaction identifier of the current transaction under the condition that a trigger condition is met; and finally, redoing the current transaction according to the acquired transaction information. Compared with the prior art, the invention does not rely on a transaction coordinator any more, but stores the transaction information for transaction processing in advance, so that when the triggering condition is met, the transaction can be re-executed directly according to the transaction information corresponding to the transaction identifier stored in advance, thereby improving the efficiency of transaction processing.
Furthermore, the embodiment stores the transaction information in the form of a table in the database, so that the transaction information with longer storage time can be cleaned in time, the storage space can be recycled, and the performance of the system can be improved.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The term "comprising", without further limitation, means that the element so defined is not excluded from the group consisting of additional identical elements in the process, method, article, or apparatus that comprises the element.
The method and apparatus for transaction processing provided by the embodiment of the present invention are described in detail above, and the principle and the embodiment of the present invention are explained herein by applying a specific example, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (2)
1. A method of transaction processing, the method comprising:
transaction information of a transaction is stored in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state, and the transaction state is divided into a redo state, a non-redo state and a redo state;
judging whether the current transaction meets a preset trigger condition, if so, acquiring transaction information corresponding to the transaction identifier of the current transaction, wherein the trigger condition comprises transaction submission failure, or the system time meets a preset period for scanning the transaction information, and meanwhile, a transaction state field in the scanned transaction information of the current transaction is not redone;
re-executing the current transaction according to the transaction information;
the pre-storing transaction information of the transaction in a database includes:
creating a plurality of tables with equal size in the database in advance; storing transaction information for a transaction in the table;
the method further comprises the following steps:
presetting a deleting condition; judging whether a table storing the transaction information in the database meets the deletion condition, if so, deleting the table;
the judging whether the current transaction meets the preset triggering condition includes:
presetting the transaction submission failure as the trigger condition;
judging whether the current transaction meets the transaction submission failure;
or,
presetting any time period as a trigger cycle;
and under the condition that the time difference between the time meeting the trigger period last time and the current time is not less than the trigger period, judging whether the transaction state of the current transaction is not redo.
2. An apparatus for transaction processing, the apparatus comprising:
the storage module is used for storing transaction information of a transaction in a database in advance, wherein the transaction information comprises a transaction identifier and a transaction state, and the transaction state is divided into a redo state, a non-redo state and a redo state;
the system comprises a first judging module, a second judging module and a third judging module, wherein the first judging module is used for judging whether the current transaction meets a preset triggering condition, the triggering condition comprises transaction submission failure, or the system time meets a preset period for scanning transaction information, and a transaction state field in the scanned transaction information of the current transaction is not redo;
the first obtaining module is used for obtaining the transaction information corresponding to the transaction identifier of the current transaction when the first judging module has a positive result;
the execution module is used for re-executing the current transaction according to the transaction information in the first acquisition module;
the memory module includes:
a creating submodule for creating a plurality of tables in the database in advance; the storage submodule is used for storing the transaction information of the transaction in the table;
the device, still include:
the first setting module is used for presetting deletion conditions; the second judgment module is used for judging whether a table for storing the transaction information in the database meets the deletion condition; the deleting module is used for deleting the table when the second judging module has a positive result;
the first judging module comprises:
the first setting submodule is used for presetting the transaction submission failure as the trigger condition;
the first judgment submodule is used for judging whether the current transaction meets the transaction submission failure;
or,
the second setting submodule is used for presetting any time period as a trigger cycle;
and the second judgment submodule is used for judging whether the transaction state of the current transaction is not redo under the condition that the time difference between the moment meeting the trigger period last time and the current moment is equal to the trigger period.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210581869.0A CN103019826B (en) | 2012-12-27 | 2012-12-27 | A kind of method and apparatus of issued transaction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210581869.0A CN103019826B (en) | 2012-12-27 | 2012-12-27 | A kind of method and apparatus of issued transaction |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103019826A CN103019826A (en) | 2013-04-03 |
| CN103019826B true CN103019826B (en) | 2016-08-03 |
Family
ID=47968457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210581869.0A Active CN103019826B (en) | 2012-12-27 | 2012-12-27 | A kind of method and apparatus of issued transaction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103019826B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572036B (en) * | 2013-10-12 | 2020-08-11 | 腾讯科技（深圳）有限公司 | Event processing method and device |
| US9336097B2 (en) * | 2014-02-27 | 2016-05-10 | International Business Machines Corporation | Salvaging hardware transactions |
| CN106445933B (en) * | 2015-08-04 | 2019-11-12 | 阿里巴巴集团控股有限公司 | A kind of data processing method and system |
| CN105786595B (en) * | 2016-02-29 | 2019-04-23 | 浪潮通用软件有限公司 | A kind of transaction control method that two-part is submitted |
| CN107230059A (en) * | 2017-05-26 | 2017-10-03 | 中国建设银行股份有限公司 | The execution method and device of on-line transaction |
| CN108090736B (en) * | 2017-12-18 | 2020-12-11 | 北京中关村科金技术有限公司 | Workflow approval bill-based approval method and device and readable storage medium |
| CN109684398A (en) * | 2018-12-24 | 2019-04-26 | 普元信息技术股份有限公司 | The system and method for data-optimized management function is realized under big data environment based on multimode |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102193986A (en) * | 2011-03-25 | 2011-09-21 | 北京世纪互联工程技术服务有限公司 | Method of implementing online transaction in graphic database |
| CN102279855A (en) * | 2010-06-10 | 2011-12-14 | 三星电子（中国）研发中心 | Device and method for treating transactions with database |
| CN102571850A (en) * | 2010-12-24 | 2012-07-11 | 中国移动通信集团山东有限公司 | Transaction committing system, method and equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102306197B (en) * | 2011-09-22 | 2013-07-03 | 用友软件股份有限公司 | Device and method for guaranteeing consistency of data-source-crossing operation results |
-
2012
- 2012-12-27 CN CN201210581869.0A patent/CN103019826B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102279855A (en) * | 2010-06-10 | 2011-12-14 | 三星电子（中国）研发中心 | Device and method for treating transactions with database |
| CN102571850A (en) * | 2010-12-24 | 2012-07-11 | 中国移动通信集团山东有限公司 | Transaction committing system, method and equipment |
| CN102193986A (en) * | 2011-03-25 | 2011-09-21 | 北京世纪互联工程技术服务有限公司 | Method of implementing online transaction in graphic database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103019826A (en) | 2013-04-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103019826B (en) | A kind of method and apparatus of issued transaction | |
| WO2016180164A1 (en) | Method and apparatus for rolling back distributed transaction | |
| KR102072726B1 (en) | Systems and methods for supporting inline delegation of middle-tier transaction logs to database | |
| CN111752957B (en) | Sale locking method and system based on caching | |
| KR101993432B1 (en) | Systems and methods for supporting transaction recovery based on a strict ordering of two-phase commit calls | |
| Brewer | CAP twelve years later: How the" rules" have changed | |
| CN106462594B (en) | System and method for massively parallel processing of database | |
| CN104699712B (en) | The method and device being updated to the inventory record information in database | |
| US20130145371A1 (en) | Batch processing of business objects | |
| CN104219235B (en) | A kind of distributed transaction requesting method and device | |
| US10204012B2 (en) | Impact analysis-based task redoing method, impact analysis calculation apparatus, and one-click resetting apparatus | |
| JP2015514247A5 (en) | ||
| US20090063807A1 (en) | Data redistribution in shared nothing architecture | |
| US9582314B2 (en) | Managing data consistency between loosely coupled components in a distributed computing system | |
| US9348841B2 (en) | Transaction processing method and system | |
| CN104809025A (en) | Method and device for enabling programs to be online | |
| WO2017128028A1 (en) | Transaction processing method and apparatus | |
| CN112765126B (en) | Database transaction management method, device, computer equipment and storage medium | |
| CN112559496B (en) | Method and device for realizing transaction atomicity of distributed database | |
| CN107688581B (en) | Data model processing method and device | |
| CN110765144B (en) | Distributed heterogeneous database data processing method and device | |
| CN114579260A (en) | Transaction processing method and system | |
| CN106897024B (en) | Data writing method and device | |
| JPH10232809A (en) | Transaction processing system | |
| CN116756160A (en) | Method and device for determining data state of database and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 100086, three or four floor, CLP information building, 6 South Avenue, Haidian District, Beijing, Zhongguancun Applicant after: ASIAINFO TECHNOLOGIES (CHINA), Inc. Address before: 100086, three or four floor, CLP information building, 6 South Avenue, Haidian District, Beijing, Zhongguancun Applicant before: Asiainfo-Linkage (China) Co.,Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: ASIAINFO-LINKAGE (CHINA) CO., LTD. TO: ASIAINFO SCIENCE + TECHNOLOGY (CHINA) CO., LTD. |
|
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 100193 Beijing city northwest of Haidian District Wang Road No. 10 hospital of eastern Asia LIAN's global R & D center headquarters building Applicant after: ASIAINFO TECHNOLOGIES (CHINA), Inc. Address before: 100086, three or four floor, CLP information building, 6 South Avenue, Haidian District, Beijing, Zhongguancun Applicant before: ASIAINFO TECHNOLOGIES (CHINA), Inc. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20161206 Address after: 100193 Beijing City, Haidian District, North East Road, No. 10, East Hospital, building, floor 4, block A, block A2 Patentee after: Beijing Asiainfo Shidai Rongchuang Consulting Co.,Ltd. Address before: 100193 Beijing city northwest of Haidian District Wang Road No. 10 hospital of eastern Asia LIAN's global R & D center headquarters building 4 floor A block A1 Patentee before: AsiaInfo software (Beijing) Co.,Ltd. voyage Effective date of registration: 20161206 Address after: 100193 Beijing city northwest of Haidian District Wang Road No. 10 hospital of eastern Asia LIAN's global R & D center headquarters building 4 floor A block A1 Patentee after: AsiaInfo software (Beijing) Co.,Ltd. voyage Address before: 100193 Beijing city northwest of Haidian District Wang Road No. 10 hospital of eastern Asia LIAN's global R & D center headquarters building Patentee before: ASIAINFO TECHNOLOGIES (CHINA), Inc. |
|
| CP01 | Change in the name or title of a patent holder |
Address after: 100193 A2, 4 floor, building 19, 19 East Tower, 10 northwestern Wang Dong Road, Haidian District, Beijing. Patentee after: Yaxin era Technology Group Ltd. Address before: 100193 A2, 4 floor, building 19, 19 East Tower, 10 northwestern Wang Dong Road, Haidian District, Beijing. Patentee before: Beijing Asiainfo Shidai Rongchuang Consulting Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |