CN104794138A - Method, device and system for determining database transaction result - Google Patents
Method, device and system for determining database transaction result Download PDFInfo
- Publication number
- CN104794138A CN104794138A CN201410030584.7A CN201410030584A CN104794138A CN 104794138 A CN104794138 A CN 104794138A CN 201410030584 A CN201410030584 A CN 201410030584A CN 104794138 A CN104794138 A CN 104794138A
- Authority
- CN
- China
- Prior art keywords
- transaction
- unique identification
- database
- trade confirmation
- confirmation table
- 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.)
- Granted
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the field of database processing and provides a method, device and system for determining a database transaction result. According to the method, device and system, a unique transaction identification recorded in a transaction determination list configured on a database server is searched for, whether transaction is successively executed or not is judged, search of feature data of transaction is not needed, the automatic transaction reversing function and the breakpoint processing function on a large batch of data are achieved, and the method, device and system are particularly suitable for processing of platform-level software and a large batch of data.
Description
Technical field
The invention belongs to database processing field, particularly relate to a kind of database transaction results verification method, Apparatus and system.
Background technology
Support in the Database Systems of transaction (Transaction) at one, atomicity (Atomicity) is the characteristic that must possess, otherwise cannot ensure the correctness of data in process of exchange (Transaction processing), process of exchange does not reach the requirement of transaction most probably.
Atomicity (Atomicity) refers to all operations in whole transaction or all completes, or does not all complete, and can not be stuck in certain link middle.Transaction makes a mistake in the process of implementation, can be rolled back (Rollback) to concluding the business the state before starting, just as this transaction never performed.
The current main flow supporting the Database Systems of transaction is relevant database, as ORACLE, DB2, SQL Server etc.Relevant database all adopts C/S framework, and database transaction action is initiated by client, and execution is responsible for by database server, and returns transaction execution result to client, and client can judge that whether transaction is successful accordingly.But when generation power down, network interruption, hardware fault or database delay the unscheduled events such as machine, client cannot obtain transaction execution result from database server, thus cannot judge whether database transaction runs succeeded.
In prior art, when client does not obtain transaction execution result from database server, in order to judge whether database transaction runs succeeded, client needs usually after fault recovery, again initiate the content search to judging to conclude the business to database server, judge whether transaction runs succeeded by the characteristic in the transaction content of inquiry.
Such as, a user message table is had in the application program of client, a field is had to be address name in this table, and the data of this field can only be unique, application program inserts data in this table, wherein the information of address name field is " Zhang San ", and these data are the characteristics in this transaction.Application program submits to this insertion to conclude the business by client-side interface to database server.Suppose before database server returns this transaction results, the network short interruption between client and database server, application program does not receive the transaction execution result that database server returns, and cannot judge that whether this transaction is successful.In this case, application program can only automatically or by manually initiate one in user message table characteristic " Zhang San " and inquiry, if these data exist in Query Result, then just think this Transaction Success, if not these data in Query Result, then just think and this Fail Transaction re-execute this data insert action.
Because the characteristic of each transaction is substantially different, lack the execution result that a kind of general way judges to conclude the business, be all generally by user by reading characteristic and confirming to confirm transaction whether success, or still will carry out other process, as re-executed transaction.
Summary of the invention
The embodiment of the present invention provides a kind of database transaction results verification method, when not needing the characteristic confirming transaction, can confirm that whether the last transaction of client is successful fast.
The embodiment of the present invention is achieved in that a kind of database transaction results verification method, and described method comprises the steps:
Generate and record transaction unique identification;
Transaction statement corresponding for described transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table are submitted to database server as a transaction;
When reception database server returns generation exception in the process of transaction execution result, initiate to database server unique identification inquiry request of concluding the business, obtain the transaction unique identification of trade confirmation table;
The transaction unique identification of the transaction unique identification obtained from trade confirmation table and client local record is contrasted, judges whether current transaction runs succeeded;
Described trade confirmation table is configured in database server;
Described transaction unique identification at least comprises the serial number of the transaction of client unique identification and successful execution.
The embodiment of the present invention also provides a kind of database transaction results verification device, and described device comprises:
Transaction unique identification generation unit, for generating and recording transaction unique identification;
Transaction statement commit unit, for submitting to database server using transaction statement corresponding for described transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table as a transaction;
Transaction unique identification acquiring unit, when occurring abnormal for returning at reception database server in the process of transaction execution result, initiating to database server unique identification inquiry request of concluding the business, obtaining the transaction unique identification of trade confirmation table; And
Transaction execution result judging unit, for being contrasted by the transaction unique identification of the transaction unique identification obtained from trade confirmation table and client local record, judges whether current transaction runs succeeded;
Described trade confirmation table is configured in database server;
Described transaction unique identification at least comprises the serial number of the transaction of client unique identification and successful execution.
The embodiment of the present invention additionally provides a kind of database transaction system, includes above-mentioned database transaction results verification device in described database transaction system.
Under the exception conditions such as the embodiment of the present invention solves disconnected, power down in a network, database is delayed, client does not need the characteristic of inquiring about transaction, just can confirm that whether last transaction is successful fast, thus realize the breakpoint processing capacity that orthofunction and data in enormous quantities are rushed in transaction automatically, be particularly useful for the process of platform class software and data in enormous quantities.
Accompanying drawing explanation
Fig. 1 is the realization flow figure of the database transaction results verification method that the embodiment of the present invention provides;
Fig. 2 is the structural drawing of the database transaction results verification device that the embodiment of the present invention provides.
Embodiment
In order to make object of the present invention, technical scheme and advantage clearly understand, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, be not intended to limit the present invention.
In embodiments of the present invention, database server configures a trade confirmation table, in this trade confirmation table, records the transaction unique identification of last successful execution.When an exception occurs, the trade confirmation table of client query database server, to judge to conclude the business whether successful execution according to the transaction unique identification of trade confirmation table record.
As one embodiment of the present of invention, transaction unique identification at least comprises following information:
1. client unique identification, is used for unique identification client.
As one embodiment of the present of invention, a client can a corresponding trade confirmation table.
As an alternative embodiment of the invention, multiple client can use a trade confirmation table, and different clients has different marks in this trade confirmation table.
2. the serial number of the transaction of successful execution, is used for the transaction of a unique identification successful execution.
In embodiments of the present invention, the serial number of the transaction of successful execution can be the Serial No. added up in order, also can be the mark of user's self-defining, such as " 20131115080531001 ", identify No. 001 transaction of 05 point of 31 seconds successful execution during 15 days 08 November in 2013.
As one embodiment of the present of invention, according to actual needs, transaction unique identification can also comprise other information of transaction, such as, be used for the type of transaction mark of the type identifying the transaction that client is initiated.
In embodiments of the present invention, different identification information in transaction unique identification, the serial number of the such as transaction of client unique identification, successful execution can be recorded in the different field in trade confirmation table respectively, also can be recorded in trade confirmation table in one or more field by they combinations.
In the embodiment of the present invention, trade confirmation table can configure in database server side by user is manual, or is automatically configured on database server by client.After having configured, the transaction unique identification of initialization trade confirmation table.
Fig. 1 shows the realization flow of the database transaction results verification method that the embodiment of the present invention provides, and details are as follows:
In step S101, generate and record transaction unique identification;
In step s 102, transaction statement corresponding for this transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table are submitted to database server as a transaction;
More New Transaction uniquely identified statement is as follows by the example of pseudo-representation:
Update trade confirmation table set transaction unique identification=' current transaction unique identification ' where client unique identification=' client id '
After transaction runs succeeded, the transaction unique identification in trade confirmation table upgrades by database server.If transaction does not run succeeded, then unique identification of concluding the business can not upgrade.
In step s 103, when reception database server returns generation exception in the process of transaction execution result, initiate to database server unique identification inquiry request of concluding the business, obtain the transaction unique identification of trade confirmation table;
In embodiments of the present invention, occur extremely if database server returns in the process of transaction execution result to client, such as during network interruption, after the connection that client is recovered with database server, initiate transaction unique identification inquiry request to database server, obtain the transaction unique identification of trade confirmation table.
Transaction unique identification inquiry request is as follows by the example of pseudo-representation:
Select transaction unique identification from trade confirmation table where client unique identification=' client id '
In step S104, the transaction unique identification of the transaction unique identification obtained from trade confirmation table and client local record is contrasted, judges whether current transaction runs succeeded.
With practical application scene, above treatment scheme is described below:
scene one:
Money transfer transactions is a common transaction in kernel business of bank system.Suppose that an account A initiates one to another one account B and transfers accounts, the amount of money of transferring accounts is 100, and credit is called TabAcc, and wherein account name field is AccName, and account balance field is AccBalance.
In embodiments of the present invention, give money transfer transactions referred to as TransAcc.Application program configuration of transaction confirmation form on database server of client, and initialization trade confirmation table.
Build predicative sentence example as follows:
Create table QueryConfirmTab（
ClientId int, // client id
TxnName varchar(20), // transaction is called for short
The serial number of TxnExecNum int//transaction of successful execution);
The application program of client, before each transaction is submitted to, generates and records the transaction unique identification of concluding the business.Transaction unique identification is made up of ClientId+TxnExecNum, and form is: ClientId_TxnExecNum.
The initial value of TxnName is null; The initial value of TxnExecNum is 0, is TransAcc_1 for first money transfer transactions in this scene; ClientId is 1.
Client starts to initiate money transfer transactions, and comprise the statement upgrading trade confirmation table in transaction statement, example is as follows:
begin;
update TabAcc Set TabBalance=TabBalance-100where TabAcc='A';
update TabAcc Set TabBalance=TabBalance+100where TabAcc='B';
update QueryConfirmTab Set TxnName='TransAcc',TxnExecNum=1
where ClientId=1;
commit;
If database server normally returns the execution result of above-mentioned transaction to client, client need not any special processing.
If there is exception, database server does not return the execution result of above-mentioned transaction to client, then client needs fill order, confirms transaction execution result.Statement example is as follows:
select TxnName,TxnExecNum from QueryConfirmTab where ClientId=1;
Now, the TxnExecNum value comprised in the transaction unique identification of TxnExecNum and local record contrasts by client, and identical expression transaction runs succeeded, otherwise represents that transaction performs failure.
scene two:
There is the customer information of more than ten million rank in a large amount of enterprises, often has the requirement needing customer profile data to import or derive.The performance issue caused for avoiding concluding the business greatly and a large amount of lock record problem, adopt batch mode to carry out concurrent transaction process usually.
The customer profile data of 10,000,000 is supposed to import in database according to the method for 10,000 a collection of mode SQL statement INSERT from file.
In order to make process prescription more clear, the embodiment of the present invention adopts simplify processes, and carry out serial processing by the mode of every 1000 one transaction, the method for parallel processing is also similar.Because the importing time of mass data is long, the very possible situation occurring exception in importing process, in order to ensure reentrying of importing process, avoid after makeing mistakes, clearing up the data imported, more again import by Article 1 record, then can occur that the progress inquiring importing process extremely becomes very important, which need to confirm successfully import to batch, thus ensure after fault recovery, therefrom breakpoint succession carries out the importing work of subsequent batches, realizes reentrying of batch data process.
In embodiments of the present invention, client's table name is CustomerInfoTab, comprises three fields:
1) id – customer ID 2) name – customer name 3) age – client age
Give batch client import transaction referred to as CIBatIn.Application program configuration of transaction confirmation form on database server of client, and initialization trade confirmation table.
Build predicative sentence example as follows:
Create table QueryConfirmTab（
ClientID int, // client id
TxnName varchar(20), // transaction is called for short
The successful execution of TxnExecNum int// batch serial number);
In this scenario, transaction unique identification is made up of ClientID+TxnName+TxnExecNum, and form is: ClientID_TxnName_TxnExecNum.Suppose that the ClientID of client is 1 in this example, namely the initial value of the initial value of ClientID to be the initial value of 1, TxnName be Null, TxnExecNum is the transaction unique identification of 0, first batch is 1_CIBatIn_1.
Before performing data import transaction, perform the action of initialization trade confirmation table, statement example is as follows:
Insert into QueryConfirmTab values(1,'null',0);
After getting out the data of present lot, initiate batch import transaction, in transaction statement, comprise the statement upgrading trade confirmation table, batch serial number of the current operation that TxnExecNum field is given.Statement example is as follows:
begin;
update QueryConfirmTab Set TxnName='CIBatIn',TxnExecNum=1where
ClientID=1;
insert into CustomerInfoTab values(:id1，:Name1，:Age1)，(:id2，:Name2，
:Age2)，……，(:id1000,:Name1000,:Age1000)
commit;
If database server normally returns the execution result of above-mentioned transaction to client, client need not any special processing.
If there is exception, database server does not return the execution result of above-mentioned transaction to client, then client needs fill order, confirms transaction execution result.Statement example is as follows:
select TxnName,TxnExecNum from QueryConfirmTab where ClientID=1;
Now, the TxnExecNum value that the transaction unique identification of TxnExecNum and local record comprises contrasts by client, and identical expression transaction runs succeeded, otherwise represents that transaction performs failure.
By batch carrying out in process that serial batch inserts, if there is fault to occur, when fault is occurred unsuccessful importing batch, database server can carry out rollback (Rollback) operation, the batch number of last success importing that what in trade confirmation table, TxnExecNum preserved is exactly.When fault recovery, again can perform import operation (reentry), now, client can proceed import operation from the next one batch of TxnExecNum, thus realizes breakpoint processing capacity.
Fig. 2 shows the structure of the database transaction results verification device that the embodiment of the present invention provides, and for convenience of explanation, illustrate only the part relevant to the embodiment of the present invention.
This device can be integrated in various database transaction system.
In embodiments of the present invention, database server is configured with trade confirmation table, record the transaction unique identification of last successful execution in this trade confirmation table, this transaction unique identification at least comprises the serial number of the transaction of client unique identification and successful execution.
As one embodiment of the present of invention, client unique identification also comprises the type of transaction mark of the type of the transaction initiated for mark client.
As one embodiment of the present of invention, the different identification information in client unique identification is recorded in the different field of trade confirmation table respectively, or combination is recorded in one or more field of trade confirmation table.
Transaction unique identification generation unit 21 generates and records transaction unique identification.
Transaction statement corresponding for this transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table are submitted to database server as a transaction by transaction statement commit unit 22.
Receive database server and return occur abnormal in the process of transaction execution result time, transaction unique identification acquiring unit 23 initiates transaction unique identification inquiry request to database server, obtains the transaction unique identification of trade confirmation table.
The transaction unique identification of the transaction unique identification that transaction unique identification acquiring unit 23 obtains by transaction execution result judging unit 24 and client local record contrasts, and judges whether current transaction runs succeeded.
In embodiments of the present invention, trade confirmation table can configure in database server side by user is manual, or is automatically configured on database server by client.After having configured, the transaction unique identification of initialization trade confirmation table.
When by client automatically on database server during configuration of transaction confirmation form, trade confirmation table dispensing unit 25 configuration of transaction confirmation form on database server, and initialization trade confirmation table.
The embodiment of the present invention can be applied in every profession and trade core application system, no matter adopt double-layer structure, three-decker or sandwich construction, the Transaction Inquiries under exception condition can be realized, realize fault transaction and automatically rush orthofunction, do not need manual operation, avoid the loss that maloperation brings.
In distributed transaction disposal system, client needs to access multiple databases of physically isolating, and between multiple database, ensure the consistance of transaction.Adopt the embodiment of the present invention, distributed transaction disposal system can confirm the stateful transaction that each database finally processes, thus ensures that the consistance of rear each database transaction occurs fault.
Based in the database replication of database journal and migratory system, adopt the invention process can confirm the transaction that target database finally processes to realize breakpoint processing capacity, improve fault-tolerant ability, improve the stability of system.
When database data process in enormous quantities, adopt the embodiment of the present invention can realize reentrying of batch processing and breakpoint processing capacity, increase substantially the efficiency of batch processing.
Under the exception conditions such as the embodiment of the present invention solves disconnected, power down in a network, database is delayed, client does not need the characteristic of inquiring about transaction, just can confirm that whether last transaction is successful fast, thus realize the breakpoint processing capacity that orthofunction and data in enormous quantities are rushed in transaction automatically, be particularly useful for the process of platform class software and data in enormous quantities.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, all any amendments done within the spirit and principles in the present invention, equivalent replacement and improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. a database transaction results verification method, is characterized in that, described method comprises the steps:
Generate and record transaction unique identification;
Transaction statement corresponding for described transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table are submitted to database server as a transaction;
When reception database server returns generation exception in the process of transaction execution result, initiate to database server unique identification inquiry request of concluding the business, obtain the transaction unique identification of trade confirmation table;
The transaction unique identification of the transaction unique identification obtained from trade confirmation table and client local record is contrasted, judges whether current transaction runs succeeded;
Described trade confirmation table is configured in database server;
Described transaction unique identification at least comprises the serial number of the transaction of client unique identification and successful execution.
2. database transaction results verification method as claimed in claim 1, it is characterized in that, described method also comprises the steps:
Configuration of transaction confirmation form on database server, and the transaction unique identification in initialization trade confirmation table.
3. database transaction results verification method as claimed in claim 1, is characterized in that, described client unique identification also comprises type of transaction mark.
4. the database transaction results verification method as described in claim 1,2 or 3, it is characterized in that, different identification information in described transaction unique identification is recorded in the different field of described trade confirmation table respectively, or combination is recorded in one or more field of described trade confirmation table.
5. a database transaction results verification device, is characterized in that, described device comprises:
Transaction unique identification generation unit, for generating and recording transaction unique identification;
Transaction statement commit unit, for submitting to database server using transaction statement corresponding for described transaction unique identification and the transaction uniquely identified statement upgraded in trade confirmation table as a transaction;
Transaction unique identification acquiring unit, when occurring abnormal for returning at reception database server in the process of transaction execution result, initiating to database server unique identification inquiry request of concluding the business, obtaining the transaction unique identification of trade confirmation table; And
Transaction execution result judging unit, for being contrasted by the transaction unique identification of the transaction unique identification obtained from trade confirmation table and client local record, judges whether current transaction runs succeeded;
Described trade confirmation table is configured in database server;
Described transaction unique identification at least comprises the serial number of the transaction of client unique identification and successful execution.
6. database transaction results verification device as claimed in claim 5, it is characterized in that, described device also comprises:
Trade confirmation table dispensing unit, for configuration of transaction confirmation form on database server, and the transaction unique identification in initialization trade confirmation table.
7. database transaction results verification device as claimed in claim 5, is characterized in that, described client unique identification also comprises type of transaction mark.
8. the database transaction results verification device as described in claim 5,6 or 7, it is characterized in that, different identification information in described transaction unique identification is recorded in the different field of described trade confirmation table respectively, or combination is recorded in one or more field of described trade confirmation table.
9. a database transaction system, is characterized in that, includes the database transaction results verification device described in the arbitrary claim of claim 5 to 8 in described database transaction system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410030584.7A CN104794138B (en) | 2014-01-22 | 2014-01-22 | A kind of database transaction result confirmation method, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410030584.7A CN104794138B (en) | 2014-01-22 | 2014-01-22 | A kind of database transaction result confirmation method, apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104794138A true CN104794138A (en) | 2015-07-22 |
| CN104794138B CN104794138B (en) | 2018-08-24 |
Family
ID=53558932
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410030584.7A Active CN104794138B (en) | 2014-01-22 | 2014-01-22 | A kind of database transaction result confirmation method, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104794138B (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105260464A (en) * | 2015-10-16 | 2016-01-20 | 北京奇虎科技有限公司 | Data storage structure conversion method and apparatus |
| CN105488670A (en) * | 2015-11-23 | 2016-04-13 | 上海银生宝电子支付服务有限公司 | Payment request processing method, apparatus and system |
| CN105608103A (en) * | 2015-10-16 | 2016-05-25 | 北京奇虎科技有限公司 | Transforming method and device of data storing structure |
| CN105653579A (en) * | 2015-12-18 | 2016-06-08 | 北京百度网讯科技有限公司 | Method and device for testing distributed transactions |
| CN107169767A (en) * | 2017-05-31 | 2017-09-15 | 深圳市长亮科技股份有限公司 | Correction method and system are rushed in transaction |
| CN107783861A (en) * | 2017-07-31 | 2018-03-09 | 平安科技（深圳）有限公司 | transaction rollback method, device, storage medium and computer equipment |
| CN108011926A (en) * | 2017-11-06 | 2018-05-08 | 中国银联股份有限公司 | A kind of file transmitting method, processing method, server and system |
| CN108255629A (en) * | 2017-09-22 | 2018-07-06 | 平安科技（深圳）有限公司 | Breakpoint data capture method and terminal device |
| CN109102292A (en) * | 2018-08-21 | 2018-12-28 | 联动优势电子商务有限公司 | A kind of method and device of monitor client operating status |
| CN109739674A (en) * | 2018-12-17 | 2019-05-10 | 网联清算有限公司 | Method for detecting abnormality, device and the storage medium of transaction data base |
| CN110458545A (en) * | 2018-05-07 | 2019-11-15 | 北京三快在线科技有限公司 | Electronic transaction processing method, server, transaction terminal and system |
| CN111369350A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Orthogonal punching easy processing method and device |
| CN112613993A (en) * | 2020-12-26 | 2021-04-06 | 中电金信软件有限公司 | Transaction data processing method and device, computer equipment and storage medium |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
| CN114299666A (en) * | 2021-12-28 | 2022-04-08 | 安徽影通智能科技有限公司 | Offline charging method of charging station |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996855A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | A method and system for keeping data consistency |
| US8140498B2 (en) * | 2009-05-18 | 2012-03-20 | Shuhei Nishiyama | Distributed database system by sharing or replicating the meta information on memory caches |
| CN102841906A (en) * | 2011-06-24 | 2012-12-26 | 阿里巴巴集团控股有限公司 | Integrated transaction processing system and transaction processing method |
| CN202632291U (en) * | 2012-05-28 | 2012-12-26 | 上海远动科技有限公司 | Distributed data statistics and processing system |
-
2014
- 2014-01-22 CN CN201410030584.7A patent/CN104794138B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996855A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | A method and system for keeping data consistency |
| US8140498B2 (en) * | 2009-05-18 | 2012-03-20 | Shuhei Nishiyama | Distributed database system by sharing or replicating the meta information on memory caches |
| CN102841906A (en) * | 2011-06-24 | 2012-12-26 | 阿里巴巴集团控股有限公司 | Integrated transaction processing system and transaction processing method |
| CN202632291U (en) * | 2012-05-28 | 2012-12-26 | 上海远动科技有限公司 | Distributed data statistics and processing system |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105260464B (en) * | 2015-10-16 | 2018-09-07 | 北京奇虎科技有限公司 | The conversion method and device of data store organisation |
| CN105608103A (en) * | 2015-10-16 | 2016-05-25 | 北京奇虎科技有限公司 | Transforming method and device of data storing structure |
| CN105260464A (en) * | 2015-10-16 | 2016-01-20 | 北京奇虎科技有限公司 | Data storage structure conversion method and apparatus |
| CN105488670A (en) * | 2015-11-23 | 2016-04-13 | 上海银生宝电子支付服务有限公司 | Payment request processing method, apparatus and system |
| CN105653579A (en) * | 2015-12-18 | 2016-06-08 | 北京百度网讯科技有限公司 | Method and device for testing distributed transactions |
| CN105653579B (en) * | 2015-12-18 | 2019-06-28 | 北京百度网讯科技有限公司 | The method and apparatus that a kind of pair of distributed transaction is tested |
| CN107169767A (en) * | 2017-05-31 | 2017-09-15 | 深圳市长亮科技股份有限公司 | Correction method and system are rushed in transaction |
| CN107169767B (en) * | 2017-05-31 | 2020-12-08 | 深圳市长亮科技股份有限公司 | Transaction processing method and system |
| WO2019024583A1 (en) * | 2017-07-31 | 2019-02-07 | 平安科技（深圳）有限公司 | Transaction rollback method and apparatus, computer device and storage medium |
| CN107783861A (en) * | 2017-07-31 | 2018-03-09 | 平安科技（深圳）有限公司 | transaction rollback method, device, storage medium and computer equipment |
| CN107783861B (en) * | 2017-07-31 | 2020-11-24 | 平安科技（深圳）有限公司 | Transaction rollback method, device, storage medium and computer equipment |
| CN108255629B (en) * | 2017-09-22 | 2020-09-22 | 平安科技（深圳）有限公司 | Breakpoint data obtaining method and terminal equipment |
| CN108255629A (en) * | 2017-09-22 | 2018-07-06 | 平安科技（深圳）有限公司 | Breakpoint data capture method and terminal device |
| CN108011926A (en) * | 2017-11-06 | 2018-05-08 | 中国银联股份有限公司 | A kind of file transmitting method, processing method, server and system |
| CN110458545A (en) * | 2018-05-07 | 2019-11-15 | 北京三快在线科技有限公司 | Electronic transaction processing method, server, transaction terminal and system |
| CN109102292A (en) * | 2018-08-21 | 2018-12-28 | 联动优势电子商务有限公司 | A kind of method and device of monitor client operating status |
| CN109102292B (en) * | 2018-08-21 | 2021-03-16 | 联动优势电子商务有限公司 | Method and device for monitoring running state of client |
| CN109739674A (en) * | 2018-12-17 | 2019-05-10 | 网联清算有限公司 | Method for detecting abnormality, device and the storage medium of transaction data base |
| CN111369350A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Orthogonal punching easy processing method and device |
| CN112613993A (en) * | 2020-12-26 | 2021-04-06 | 中电金信软件有限公司 | Transaction data processing method and device, computer equipment and storage medium |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
| CN114299666A (en) * | 2021-12-28 | 2022-04-08 | 安徽影通智能科技有限公司 | Offline charging method of charging station |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104794138B (en) | 2018-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104794138A (en) | Method, device and system for determining database transaction result | |
| EP3117349B1 (en) | System and method for massively parallel processing database | |
| KR102437664B1 (en) | System and method for transaction recovery in a multitenant application server environment | |
| CN102073540B (en) | Distributed affair submitting method and device thereof | |
| US9021461B2 (en) | Method and system for minimizing or eliminating downtime when updating a website | |
| KR102072726B1 (en) | Systems and methods for supporting inline delegation of middle-tier transaction logs to database | |
| KR101993432B1 (en) | Systems and methods for supporting transaction recovery based on a strict ordering of two-phase commit calls | |
| US20200272452A1 (en) | Automated transparent distribution of updates to server computer systems in a fleet | |
| CN107464151B (en) | Order data processing method and device for high-concurrency service | |
| US20110184915A1 (en) | Cluster restore and rebuild | |
| CN108647357B (en) | Data query method and device | |
| CN105608086A (en) | Transaction processing method and device of distributed database system | |
| CN103092903A (en) | Database Log Parallelization | |
| CN104809202A (en) | Database synchronization method and device | |
| US20210286799A1 (en) | Automated transaction engine | |
| CN111522631A (en) | Distributed transaction processing method, device, server and medium | |
| CN104809200A (en) | Database synchronization method and device | |
| CN105574187A (en) | Duplication transaction consistency guaranteeing method and system for heterogeneous databases | |
| CN106991606B (en) | Transaction data processing method and device | |
| CN103019826A (en) | Method and device for processing events | |
| CN103729391A (en) | Client apparatus and database server for resumable transaction and method thereof | |
| CN105938446A (en) | Data copying and fault-tolerance method based on support of RDMA and HTM | |
| US9311330B1 (en) | Method and system for performing full backup in a failover cluster | |
| WO2016165540A1 (en) | Data transfer method and device | |
| WO2022251238A1 (en) | Systems and methods for ensuring quality of search system data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |