CN102103642B - Data-erasure method based on OLTP, system and graphic data base server - Google Patents
Data-erasure method based on OLTP, system and graphic data base server Download PDFInfo
- Publication number
- CN102103642B CN102103642B CN201110074497.8A CN201110074497A CN102103642B CN 102103642 B CN102103642 B CN 102103642B CN 201110074497 A CN201110074497 A CN 201110074497A CN 102103642 B CN102103642 B CN 102103642B
- Authority
- CN
- China
- Prior art keywords
- data record
- transaction journal
- data
- transaction
- record
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the present application discloses a kind of data-erasure method based on online transaction processing system OLTP, system and graphic data base server, the method includes: reception client, by calling the data-delete command of application programming interface API transmission, comprises Transaction Identifier, nodename and filtercondition in described data-delete command；Search transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found；Search nodal community status information table according to nodename, from described nodal community status information table, obtain the data record meeting described filtercondition；The data record of filtercondition is met described in deleting one by one.Application the embodiment of the present application can realize the deletion of the data record on multiple nodes that an office relates to, it is ensured that the synchronicity of data deletion and integrity；And when affairs lost efficacy, data recovery can be carried out by rolling back action, it is ensured that the integrity of data base.
Description
Technical field
The application relates to technical field of data processing, particularly relates to a kind of data-erasure method based on OLTP (On-LineTransactionProcessing, online transaction processing system), system and graphic data base server.
Background technology
OLTP is the system of change between the data that timely collection is associated with affairs, and shared data bank and other file.When carrying out Transaction Processing, pending initial data can be immediately communicated to calculating center and process, and provides result in a short period of time, to realize processing the instant of data and immediate acknowledgment.
In OLTP system based on distributed environment, need to safeguard the integrity of data base, in prior art, Operating Complexity due to OLTP, and the demand rapidly inputting/exporting, most of OLTP realize on large computer system, when affairs relate to multiple nodes (Node) are upper delete data time, easily cause the rewriting of data and asynchronous；Further, especially when affairs lost efficacy, it is difficult to recover, be easily caused data base imperfect.
Summary of the invention
The embodiment of the present application provides a kind of data-erasure method based on OLTP, system and graphic data base server, easily causes rewriting data and nonsynchronous problem during to solve data deletion in existing distributed OLTP.
In order to solve above-mentioned technical problem, the embodiment of the present application discloses following technical scheme:
A kind of data-erasure method based on online transaction processing system OLTP, including:
Reception client, by calling the data-delete command of application programming interface API transmission, comprises Transaction Identifier, nodename and filtercondition in described data-delete command；
Search transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found；
Search nodal community status information table according to nodename, from described nodal community status information table, obtain the data record meeting described filtercondition；
The data record of filtercondition is met described in deleting one by one.
Also include:
Receive client and create order by the affairs calling API transmission；
Create order according to described affairs in transaction attributes status information table, generate a new transaction journal, and be that described new transaction journal distributes unique Transaction Identifier；
It is set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
Described search after transaction journal according to described Transaction Identifier, also include:
Judge whether to find described transaction journal；
When not finding described transaction journal, terminate flow process, when finding described transaction journal, it is judged that whether the submission attribute of the described transaction journal found and rollback attribute are and are not carried out；
When judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process.
Before meeting the data record of filtercondition described in described deletion one by one, also include:
Determine whether that data record is locked by other affairs；
When described data record is not the most by other transactional lock timing, the operation of the data record meeting filtercondition is deleted one by one described in execution, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return the described operation searching transaction journal according to described Transaction Identifier.
The data record meeting filtercondition described in described deletion one by one includes:
Described data record is formed queue；
Order extracts a data record from described queue；
When the data record of described extraction is not dirty data, and unmarked for updating and deleting time, then labelling is deleted described data record, and the associated data record of described data record, and physics and is deleted the dirty data of described associated data record；
When the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and physics deletes the associated data record of described data record；
When the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and physics deletes the dirty data of described associated data record.
Also include:
After completing to meet described in deleting one by one the data record of filtercondition, the affairs performing data deletion submit operation to；Or, the data record after deleting is carried out rolling back action.
Described affairs submit to operation to include:
Receive client by calling the Transaction Identifier of application programming interface API transmission；
The transaction journal of correspondence is found according to described Transaction Identifier；
When finding effective transaction journal, the submission attribute of described transaction journal is set to executed；
Delete the data record of locking, and the associated data record of described data record；
Described transaction journal is deleted from described transaction attributes status information table.
Described rolling back action includes:
Receive client by calling the Transaction Identifier of application programming interface API transmission；
The transaction journal of correspondence is found according to described Transaction Identifier；
When finding effective transaction journal, the rollback attribute of described transaction journal is set to executed；
Release the locking to described data record, and the locking of the associated data record of described data record；
Described transaction journal is deleted from described transaction attributes status information table.
A kind of data deletion system based on OLTP, including: graphic data base server and client side,
Described client, for the API by calling graphic data base server, to described graphic data base server transmission data delete command, comprises Transaction Identifier, nodename and filtercondition in described data-delete command；
Described graphic data base server, for searching transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found, nodal community status information table is searched according to nodename, from described nodal community status information table, obtain the data record meeting described filtercondition, described in deletion, meet the data record of filtercondition one by one.
Described client, is additionally operable to the API by calling graphic data base server, creates order to described graphic data base server transport affairs；
Described graphic data base server, it is additionally operable to create order according to described affairs in transaction attributes status information table, generates a new transaction journal, and be that described new transaction journal distributes unique Transaction Identifier, it is set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
Described graphic data base server, it is additionally operable to judge whether to find described transaction journal, when not finding described transaction journal, terminate flow process, when finding described transaction journal, judge whether submission attribute and the rollback attribute of the described transaction journal found are and are not carried out, when judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, flow process is terminated.
Described graphic data base server, it is additionally operable to determine whether that data record is locked by other affairs, when described data record is not the most by other transactional lock timing, the operation of the data record meeting filtercondition is deleted one by one described in execution, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return the described operation searching transaction journal according to described Transaction Identifier.
Described graphic data base server, after being additionally operable to meet described in deleting one by one the data record of filtercondition, the affairs performing data deletion submit operation to, or the data record after deleting is carried out rolling back action.
A kind of graphic data base server, including:
Receive unit, be used for the data-delete command receiving client by calling the transmission of application programming interface API, described data-delete command comprises Transaction Identifier, nodename and filtercondition；
Search unit, for searching transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found；
Acquiring unit, for searching nodal community status information table according to nodename, obtains the data record meeting described filtercondition from described nodal community status information table；
Delete unit, for meeting the data record of filtercondition described in deletion one by one.
State reception unit, be additionally operable to receive client and create order by the affairs calling API transmission；
Also include:
Signal generating unit, generates a new transaction journal in transaction attributes status information table for creating order according to described affairs, and is that described new transaction journal distributes unique Transaction Identifier；
Unit is set, for being set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
Also include:
First judging unit, is used for judging whether to find described transaction journal；
First performance element, for when not finding described transaction journal, terminates flow process；
Described first judging unit, is additionally operable to when finding described transaction journal, it is judged that whether the submission attribute of the described transaction journal found and rollback attribute are and are not carried out；
Described first performance element, be additionally operable to when judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process.
Also include:
Second judging unit, is used for determining whether that data record is locked by other affairs；
Second performance element, for when described data record is the most by the timing of other transactional lock, triggering described deletion unit and perform operation, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, returns described lookup unit and performs operation.
Described deletion unit includes:
Queue signal generating unit, forms queue by described data record；
Record extraction unit, order extracts a data record from described queue；
Labelling deletes unit, for not being dirty data when the data record of described extraction, and unmarked for updating and deleting time, then labelling is deleted described data record, and the associated data record of described data record, and physics and is deleted the dirty data of described associated data record；
Described labelling deletes unit, is additionally operable to when the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and physics deletes the associated data record of described data record；
Described labelling deletes unit, it is additionally operable to when the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and physics deletes the dirty data of described associated data record.
Also include:
Submit unit to, after be used for meeting described in deleting one by one the data record of filtercondition, perform the affairs of data deletion and submit to and operate；
Rollback unit, for carrying out rolling back action to the data record after deleting.
Described submission unit includes:
Mark receives unit, receives client by calling the Transaction Identifier of application programming interface API transmission；
Record search unit, finds the transaction journal of correspondence according to described Transaction Identifier；
Attribute arranges unit, when finding effective transaction journal, the submission attribute of described transaction journal is set to executed；
Unit deleted in record, for deleting the data record of locking, and the associated data record of described data record, described transaction journal is deleted from described transaction attributes status information table.
Described rollback unit includes:
Mark receives unit, for receiving client by calling the Transaction Identifier of application programming interface API transmission；
Record search unit, for finding the transaction journal of correspondence according to described Transaction Identifier；
Attribute arranges unit, for when finding effective transaction journal, the rollback attribute of described transaction journal is set to executed；
Latch-release unit, for releasing the locking to described data record, and the locking of the associated data record of described data record；
Unit deleted in record, for described transaction journal being deleted from described transaction attributes status information table.
As can be seen from the above-described embodiment, after in the embodiment of the present application, reception client is by calling the data-delete command that application programming interface API is transmitted, transaction journal is searched according to the Transaction Identifier in this delete command, and nodename is added in the effective transaction journal found, nodal community status information table is searched according to the nodename in this delete command, from nodal community status information table, obtain the data record meeting filtercondition, described in deletion, meet the data record of filtercondition one by one.Application the embodiment of the present application can meet the Operating Complexity of OLTP, and the demand rapidly inputting/exporting, it is achieved the deletion of the data record on multiple nodes that an office relates to, it is ensured that the synchronicity of data deletion and integrity；And when affairs lost efficacy, data recovery can be carried out by rolling back action, it is ensured that the integrity of data base.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present application or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, for those of ordinary skills, on the premise of not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the embodiment flow chart of the application data-erasure method based on OLTP；
Fig. 2 is the configuration diagram of the OLTP in the embodiment of the present application；
Fig. 3 is the flow chart creating new affairs in the application application example；
Fig. 4 by the application application example to the flow chart deleted of data in the new affairs of establishment；
Fig. 5 is the flow chart in the application application example deleted data record；
Fig. 6 is the flow chart that amended data carry out in the application application example affairs submission；
Flow chart when Fig. 7 is that amended data carry out in the application application example transaction rollback；
Fig. 8 is the embodiment block diagram of the application data deletion based on OLTP system；
Fig. 9 is the first embodiment block diagram of the application graphic data base server；
Figure 10 is the first embodiment block diagram of the application graphic data base server；
Figure 11 is the 3rd embodiment block diagram of the application graphic data base server.
Detailed description of the invention
Below embodiment of the present invention provides a kind of data-erasure method based on OLTP, system and graphic data base server.
For the technical scheme making those skilled in the art be more fully understood that in the embodiment of the present invention, and it is understandable to enable the above-mentioned purpose of the embodiment of the present invention, feature and advantage to become apparent from, below in conjunction with the accompanying drawings technical scheme in the embodiment of the present invention is described in further detail.
See Fig. 1, for the embodiment flow chart of the application data-erasure method based on OLTP:
Step 101: reception client, by calling the data-delete command of API transmission, comprises Transaction Identifier, nodename and filtercondition in this data-delete command.
Further, before receiving data modification order, also include the step creating affairs, i.e. receive client and create order by the affairs calling API transmission, create order according to described affairs in transaction attributes status information table, generate a new transaction journal, and be that the transaction journal that this is new distributes unique Transaction Identifier, then it is set to be not carried out by submission attribute and the rollback attribute of transaction journal.
Step 102: search transaction journal according to Transaction Identifier, and nodename is added in the effective transaction journal found.
When searching transaction journal according to Transaction Identifier, further determine whether to find described transaction journal, when not finding described transaction journal, terminate flow process, when finding described transaction journal, judge whether submission attribute and the rollback attribute of the described transaction journal found are and are not carried out, when judge be not carried out time, the transaction journal found described in determining is effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, flow process is terminated.
Step 103: search nodal community status information table according to nodename, obtains the data record meeting described filtercondition from nodal community status information table.
Step 104: delete the data record meeting filtercondition one by one.
Before deleting data record, further, determine whether that data record is locked by other affairs, when described data record is not the most by other transactional lock timing, the operation of the data record meeting filtercondition is deleted one by one described in execution, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return the described operation searching transaction journal according to described Transaction Identifier.
When deleting data record, described data record is formed queue, order extracts a data record from described queue, when the data record of described extraction is not dirty data, and unmarked for update and delete time, then labelling deletes described data record, and the associated data record of described data record, and the dirty data of the physics described associated data record of deletion, when the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and the associated data record of the physics described data record of deletion, when the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and the dirty data of the physics described associated data record of deletion.
Further, this embodiment also includes that affairs submit operation to, particularly as follows: receive client by calling the Transaction Identifier of application programming interface API transmission, the transaction journal of correspondence is found according to described Transaction Identifier, when finding effective transaction journal, the submission attribute of described transaction journal is set to executed, deletes the data record of locking, and the associated data record of described data record, described transaction journal is deleted from described transaction attributes status information table.
Further, this embodiment also includes that transaction rollback operates, particularly as follows: receive client by calling the Transaction Identifier of application programming interface API transmission, the transaction journal of correspondence is found according to described Transaction Identifier, when finding effective transaction journal, the rollback attribute of described transaction journal is set to executed, release the locking to described data record, and the locking of the associated data record of described data record, described transaction journal is deleted from described transaction attributes status information table.
See Fig. 2, for the configuration diagram of OLTP in the embodiment of the present application:
This OLTP is divided into three layers from top to bottom, and the superiors are the API (ApplicationProgrammingInterface, application programming interface) for external call routine call；Intermediate layer is the affair logic key-course, it is divided into synchronization zone and asynchronous district according to the difference of class of operation, wherein synchronization zone can only perform an operation in the same time, other operation is waited for when entering synchronization zone, in the embodiment of the present application, data deletion process is the operation completed in synchronization zone, operation in asynchronous district is unrestricted, all can operate any time；Orlop is that data storage DataSet operates level of abstraction, saves the attribute information on the attribute information of online transaction, and online transaction data to be processed place node in different attribute status information table DataSet respectively.
In graphic data base, the status information of online transaction can be stored in the attribute status information table DataSet of entitled graphic_db_tx_def, and the data structure of this DataSet is as shown in table 1 below:
Table 1
In graphic data base, each back end (Node) all has a corresponding attribute status information table DataSet of the same name, in DataSet, each data record is in addition to comprising data content, further comprises the related information of data, it comprises the attribute information of as shown in table 2 below two row field, wherein, related information can also individually be saved in the DataSet of entitled graphic_db_relation_record_def:
Table 2
Below based on the aforementioned description to OLTP framework, enumerate an application example and the application data-erasure method process is described.
See Fig. 3, for the application application example creates in OLTP system the flow chart of new affairs:
Step 301: receiving the command API that client sends, this call instruction is used for creating affairs.
Step 302: generate globally unique affairs ID for affairs to be created.
Step 303: obtain the system time of current OLTP.
Step 304: insert a new transaction journal in transaction attributes status information table, and affairs ID and system time are write in this new record.
Wherein, transaction attributes status information table is graphic_db_tx_def, and the new transaction journal wherein inserted is as shown in table 3 below:
Table 3
| tx_no | is_commit | is_rollback | is_timeout | start_time | associate_node | processing |
| 123abc | -1 | -1 | -1 | 1291739790803 | null | -1 |
See Fig. 4, by the flow chart deleted of data in the new affairs of establishment:
Step 401: client program calls API.
Affairs ID and data to be deleted, by calling API, are passed to graphic data base server by client-side program.
Wherein, the parameter being passed in graphic data base by calling API includes:
Tx_no, which affairs to be modified by instruction；
Node_name, it is intended that the data in which Node will be deleted；
Filter, filters the filtercondition of qualified data record.
Step 402: enter synchronization zone.
Wherein, synchronization zone can utilize the synchronized synchronizing thread locking of Java language to realize, and i.e. at synchronization, only an operation can enter synchronization zone.
Step 403: judge that affairs are the most effective, the most then perform step 404；Otherwise, flow process is terminated.
When judging that affairs are the most effectively, needing to inquire about graphic_db_tx_def table, and retrieve as filtercondition using affairs ID, if there is following situation, then affairs are invalid:
Record does not find；
In record, the value of is_commit is 1, illustrates that affairs have been filed on；
In record, the value of is_rollback is 1, and affairs rollback is described；
In record, the value of is_timeout is 1, illustrates that affairs are out of date；
If affairs are invalid, then this calls end, returns error message, otherwise, continues follow-up flow process.
Step 404: open issued transaction labelling.
Inquiry graphic_db_tx_def table, it is assumed that affairs ID (tx_no) are 123abc, then be set to 1 by the value of these processing recorded row, as shown in table 4 below:
Table 4
| tx_no | is_commit | is_rollback | is_timeout | Start_time | associate_node | processing |
| 123abc | -1 | -1 | -1 | 1291739790803 | null | 1 |
Step 405: flag data collection changes.
Node (associate_node) title of the node this operation related to increases in transaction journal.Assuming that in the affairs of numbered 123abc, after client program calls API, insert data in the Node of entitled Customer, the most as shown in table 5 below:
Table 5
| tx_no | is_commit | is_rollback | is_timeout | Start_time | associate_node | processing |
| 123abc | -1 | -1 | -1 | 1291739790803 | Customer | 1 |
In same affairs, if relate to the data modification to multiple nodes, then by the title of multiple nodes with CSV.
Step 406: determine data to be deleted.
Using filtration parameter incoming during client program calls API as filtercondition, filtering the data in the DataSet identical with API parameter node_name title, all data matched with filtercondition are data record to be deleted.
Step 407: check whether data are locked, the most then perform step 412；Otherwise, step 408 is performed.
Checking each data record to be deleted, if the value having any data record _ dirty row is-1, and the value of _ tx_no row is neither also not equal to Current transaction ID for sky, then it represents that there is data record in data record to be deleted and is locked by other affairs.
Step 408: delete data record one by one.
When whole data to be deleted are not the most by other transactional lock timings, then whole data records to be deleted can be formed a queue, each data record is carried out deletion action.Concrete deletion action process may refer to the flow process described in subsequent figure 5.
Step 409: update the timestamp of affairs.
Up-to-date system time is updated in the start_time row of affiliated transaction journal.Assuming that Current transaction ID is 123abc, current system time is 1291739798888, then the data after updating are as shown in table 6 below:
Table 6
| tx_no | is_commit | is_rollback | is_timeout | Start_time | associate_node | processing |
| 123abc | -1 | -1 | -1 | 1291739798888 | Customer | 1 |
Step 410: close issued transaction labelling.
Inquiry graphic_db_tx_def table, it is assumed that affairs ID are 123abc, then be set to-1 by the value of these processing recorded row, as shown in table 7 below:
Table 7
| tx_no | is_commit | is_rollback | is_timeout | start_time | associate_node | processing |
| 123abc | -1 | -1 | -1 | 1291739798888 | Customer | -1 |
Step 411: exit synchronization zone, terminates flow process.
Jump out the locking of aforementioned synchronized synchronizing thread.
Step 412: wait 10 milliseconds.
I.e. perform the thread dormancy 10 milliseconds of current logic.This time span can also carry out other as required and arrange, and the embodiment of the present application does not limits.
Step 413: judge that affairs are the most overtime, the most then terminate flow process；Otherwise, step 402 is returned.
In the Current transaction record of graphic_db_tx_def table, deduct the value of transaction journal start_time row with the time of current system, if difference is more than 30000 (i.e. 30 seconds), then show that affairs have timed out, terminate current process, otherwise, be again introduced into synchronization zone.
See Fig. 5, for applying for the flow chart in application example, data deleted one by one, i.e. to the specific descriptions of step 408 in Fig. 4:
Step 501: obtain the length of data queue to be deleted.
Step 502: judge whether queue length is empty, the most then terminate flow process；Otherwise, step 503 is performed.
If queue length is empty (being 0), then means that queue has not had data to record pending, therefore terminate flow process.
Step 503: take out a data record from the queue of data to be deleted.
Step 504: judge whether this data record is dirty data, the most then perform step 510；Otherwise, step 505 is performed.
Check data record _ dirty row value, if the value of these row is 1, then means that this data is recorded as dirty data, be not.
Step 505: check that this data is the most labeled and delete, the most then return step 501；Otherwise, step 506 is performed.
Wherein, when meeting following condition, represent that this data record is labeled and delete:
This data record _ tx_no row value equal with things ID of Current transaction；Or,
The value that there are not, _ dirty identical with the Record ID of current data record row in the DataSet of the same name of present node is 1, the data record that value is Current transaction ID of _ tx_no row.
Delete if this data record is labeled, represent in the operation before Current transaction, this data record is deleted, therefore ignore this data record, reexamine queue length, process next data record, otherwise, continue executing with subsequent step.
Step 506: check that this data is the most labeled and update, the most then perform step 512；Otherwise, step 507 is performed.
This data record _ tx_no row value equal with affairs ID of Current transaction；Or,
The value that can find, _ dirty identical with the Record ID of current data row in the DataSet of the same name of present node is 1, the copy record that value is Current transaction numbering of _ tx_no row.
Update if this data record is labeled, represent in the operation before Current transaction, this data record had been performed amendment operation, has then performed step 512, otherwise, continue executing with subsequent step.
Step 507: labelling deletion record.
By this data record _ tx_no row value be revised as current affairs ID.
Step 508: labelling deletes the Relation of data record.
The DataSet of entitled graphic_db_relation_record_def searches, filter all source_record row or target_record row value equal to the Record ID of this data record, _ dirty row the Relation data record that value is-1, by these Relation data records _ tx_no row value be set to Current transaction ID.
Step 509: physics deletes Relation dirty data, returns step 501.
The DataSet of entitled graphic_db_relation_record_def searches, filter the value of all source_record row or target_record row equal to the Record ID of this data record, the Relation data record that value is 1 of _ dirty row, these Relation data records are deleted from DataSet, returns step 501.
Step 510: judge whether dirty data is newly inserted, the most then perform step 511；Otherwise, step 501 is returned.
, the data record that value be-1 of _ dirty row identical with the data Record ID of current data record is searched in DataSet, if it is found, then represent that current data is the dirty data copy of this data record, ignores current data record, reexamine queue length, process next data record；If can not find, then it represents that current data record is newly inserted dirty data.
Step 511: physics deletes data record, and Relation dirty data, returns step 501.
Step 512: delete this transcript, labelling deletes Relation, and physics deletes Relation dirty data, returns step 501.
First, after deleting this data transcript.
Secondly, labelling deletes Relation.The DataSet of entitled graphic_db_relation_record_def searches, filter all source_record row or target_record row value equal to the data Record ID of this data record, _ dirty row the Relation data record that value is-1, by these Relation data records _ tx_no row value be set to Current transaction ID.
Finally, physics deletes Relation dirty data.The DataSet of entitled graphic_db_relation_record_def searches, filter the Relation data record that value is 1 that the value of all source_record row or target_record row arranges equal to the data Record ID of this data record, _ dirty, these Relation data records are deleted from DataSet.
See Fig. 6, for the application the data after deleting carried out the flow process of things submission:
Step 601: client call API.
Affairs ID, by calling API, are transferred to graphic data base by client-side program.
Step 602: judge that affairs are the most effective, the most then perform step 603；Otherwise, flow process is terminated.
Judging that the most effective mechanism of affairs is to inquire about graphic_db_tx_def table using affairs ID as filtercondition, if there is following situation, then affairs are invalid:
Record does not find；
In record, the value of is_commit is 1, illustrates that affairs have been filed on；
In record, the value of is_rollback is 1, and affairs rollback is described；
In record, the value of is_timeout is 1, illustrates that affairs are out of date；
If affairs are invalid, then this calls end, returns error message, otherwise, continues executing with follow-up flow process.
Step 603: labelling affairs submit state to.
Inquiry graphic_db_tx_def table, it is assumed that affiliated affairs ID are 123abc, then be set to 1 by value of this record is_commit row, as shown in table 8 below:
Table 8
| tx_no | is_commit | is_rollback | is_timeout | Start_time | associate_node | processing |
| 123abc | 1 | -1 | -1 | 1291739790803 | Customer | -1 |
Step 604: delete locking data.
The value of associate_node row in transaction journal belonging in inquiry graphic_db_tx_def table, the value assuming these row is Customer, then Query Name is the DataSet of Customer, by this DataSet _ dirty row value be-1, _ tx_no row value be when affairs ID record delete.
Step 605: delete Relation.
Inquiry graphic_db_relation_record_def table, filter in this DataSet _ value of dirty row is-1, the value of _ tx_no row all data records equal to Current transaction ID, these data records are deleted from DataSet.
Step 606: delete transaction journal.
The record that this submits to affairs is deleted from the table of entitled graphic_db_tx_def, completes the submission operation of affairs.
See Fig. 7, the flow chart when data after deleting being carried out transaction rollback for the application:
Step 701: client call API.
Affairs ID, by calling API, are transferred to graphic data base by client-side program.
Step 702: judge that affairs are the most effective, the most then perform step 703；Otherwise, flow process is terminated.
When judging that affairs are the most effectively, needing to inquire about graphic_db_tx_def table, and retrieve as filtercondition using affairs ID, if there is following situation, then affairs are invalid:
Record does not find；
In record, the value of is_commit is 1, illustrates that affairs have been filed on；
In record, the value of is_rollback is 1, and affairs rollback is described；
In record, the value of is_timeout is 1, illustrates that affairs are out of date；
If affairs are invalid, then this calls end, returns error message, otherwise, continues follow-up flow process.
Step 703: labelling transaction rollback state.
Inquiry graphic_db_tx_def, it is assumed that the numbered 123abc of affiliated affairs, is set to 1 by the value that this data record is_rollback arranges, as follows:
Table 9
| tx_no | is_commit | is_rollback | is_timeout | Start_time | associate_node | processing |
| 123abc | -1 | 1 | -1 | 1291739790803 | Customer | -1 |
Step 704: release data interlock.
Transaction journal belonging in inquiry graphic_db_tx_def table arranges the value of associate_node, the value assuming these row is Customer, then inquire about the DataSet of entitled Customer, filter in this DataSet _ the value of dirty row is equal to-1, the value of _ tx_no row is equal to Current transaction ID record, by these data records _ value of tx_no row is revised as null.
Step 705: release Relation locking.
Inquiry graphic_db_relation_record_def table, filters in this DataSet _ the value of dirty row is equal to-1, the value of _ tx_no row is equal to Current transaction ID data record, by these data records _ value of tx_no row is revised as null.
Step 706: delete transaction journal.
The data record of these rollback affairs is deleted from the table of entitled graphic_db_tx_def, completes the rolling back action of affairs.
The embodiment of data-erasure method based on OLTP with the application is corresponding, present invention also provides data deletion system based on OLTP and the embodiment of graphic data base server.
See Fig. 8, for the embodiment block diagram of the application data deletion based on OLTP system:
Should data deletion system based on OLTP include: client 810 and graphic data base server 820.
Wherein, described client 810, for the API by calling graphic data base server, to described graphic data base server transmission data delete command, described data-delete command comprises Transaction Identifier, nodename and filtercondition；
Described graphic data base server 820, for searching transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found, nodal community status information table is searched according to nodename, from described nodal community status information table, obtain the data record meeting described filtercondition, described in deletion, meet the data record of filtercondition one by one.
Further, described client 810, it is additionally operable to the API by calling graphic data base server, creates order to described graphic data base server transport affairs；Described graphic data base server 820, it is additionally operable to create order according to described affairs in transaction attributes status information table, generates a new transaction journal, and be that described new transaction journal distributes unique Transaction Identifier, it is set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
Further, described graphic data base server 820, it is additionally operable to judge whether to find described transaction journal, when not finding described transaction journal, terminate flow process, when finding described transaction journal, judge whether submission attribute and the rollback attribute of the described transaction journal found are and are not carried out, when judge be not carried out time, the transaction journal found described in determining is effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process.
Further, described graphic data base server 820, it is additionally operable to determine whether that data record is locked by other affairs, when described data record is not the most by other transactional lock timing, the operation of the data record meeting filtercondition is deleted one by one described in execution, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return the described operation searching transaction journal according to described Transaction Identifier.
Further, described graphic data base server 820, after being additionally operable to meet described in deleting one by one the data record of filtercondition, the affairs performing data deletion submit operation to, or the data record after deleting is carried out rolling back action.
See Fig. 9, for the first embodiment block diagram of the application graphic data base server:
This graphic data base server includes: receives unit 910, searches unit 920, acquiring unit 930 and delete unit 940.
Wherein, receive unit 910, be used for the data-delete command receiving client by calling the transmission of application programming interface API, described data-delete command comprises Transaction Identifier, nodename and filtercondition；
Search unit 920, for searching transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found；
Acquiring unit 930, for searching nodal community status information table according to nodename, obtains the data record meeting described filtercondition from described nodal community status information table；
Delete unit 940, for meeting the data record of filtercondition described in deletion one by one.
See Figure 10, for the second embodiment block diagram of the application graphic data base server:
This graphic data base server includes: receives unit 1001, signal generating unit 1002, arranges unit 1003, lookup unit the 1004, first judging unit the 1005, first performance element 1006, acquiring unit the 1007, second judging unit the 1008, second performance element 1009 and delete unit 1010.
State reception unit 1001, create order for receiving client by the affairs calling API transmission；
Signal generating unit 1002, generates a new transaction journal in transaction attributes status information table for creating order according to described affairs, and is that described new transaction journal distributes unique Transaction Identifier；
Unit 1003 is set, for being set to be not carried out by submission attribute and the rollback attribute of described transaction journal；
Receive unit 1001, be additionally operable to the data-delete command receiving client by calling the transmission of application programming interface API, described data-delete command comprises Transaction Identifier, nodename and filtercondition；
Search unit 1004, for searching transaction journal according to described Transaction Identifier；
First judging unit 1005, is used for judging whether to find described transaction journal；
First performance element 1006, for when not finding described transaction journal, terminates flow process；
Described first judging unit 1005, is additionally operable to when finding described transaction journal, it is judged that whether the submission attribute of the described transaction journal found and rollback attribute are and are not carried out；
Described first performance element 1006, be additionally operable to when judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process；
Acquiring unit 1007, for searching nodal community status information table according to nodename, obtains the data record meeting described filtercondition from described nodal community status information table；
Second judging unit 1008, is used for determining whether that data record is locked by other affairs；
Second performance element 1009, for when described data record is not the most by other transactional lock timing, triggering described deletion unit 1010 and perform operation, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return described lookup unit 1004 and perform operation；
Delete unit 1010, for meeting the data record of filtercondition described in deletion one by one.
Concrete, delete unit 1010 and can include (not shown in Figure 10): queue signal generating unit, described data record is formed queue；Record extraction unit, order extracts a data record from described queue；Labelling deletes unit, for not being dirty data when the data record of described extraction, and unmarked for updating and deleting time, then labelling is deleted described data record, and the associated data record of described data record, and physics and is deleted the dirty data of described associated data record；Described labelling deletes unit, is additionally operable to when the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and physics deletes the associated data record of described data record；Described labelling deletes unit, it is additionally operable to when the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and physics deletes the dirty data of described associated data record.
See Figure 11, for the 3rd embodiment block diagram of the application graphic data base server:
This graphic data base server includes: receives unit 1110, search unit 1120, acquiring unit 1130, deletion unit 1140, submission unit 1150 and rollback unit 1160.
Receive unit 1110, be used for the data-delete command receiving client by calling the transmission of application programming interface API, described data-delete command comprises Transaction Identifier, nodename and filtercondition；
Search unit 1120, for searching transaction journal according to described Transaction Identifier, and described nodename is added in the effective transaction journal found；
Acquiring unit 1130, for searching nodal community status information table according to nodename, obtains the data record meeting described filtercondition from described nodal community status information table；
Delete unit 1140, for meeting the data record of filtercondition described in deletion one by one；
Submit unit 1150 to, after be used for meeting described in deleting one by one the data record of filtercondition, perform the affairs of data deletion and submit to and operate；
Rollback unit 1160, for carrying out rolling back action to the data record after deleting.
Concrete, submit to unit 1150 can include (not shown in Figure 11): mark receives unit, receive client by calling the Transaction Identifier of application programming interface API transmission；Record search unit, finds the transaction journal of correspondence according to described Transaction Identifier；Attribute arranges unit, when finding effective transaction journal, the submission attribute of described transaction journal is set to executed；Unit deleted in record, for deleting the data record of locking, and the associated data record of described data record, described transaction journal is deleted from described transaction attributes status information table.
Concrete, rollback unit 1160 can include (not shown in Figure 11): mark receives unit, for receiving client by calling the Transaction Identifier of application programming interface API transmission；Record search unit, for finding the transaction journal of correspondence according to described Transaction Identifier；Attribute arranges unit, for when finding effective transaction journal, the rollback attribute of described transaction journal is set to executed；Latch-release unit, for releasing the locking to described data record, and the locking of the associated data record of described data record；Unit deleted in record, for described transaction journal being deleted from described transaction attributes status information table.
By the description to embodiment of above, in the embodiment of the present application after graphic data base server receives the data modification order that client is transmitted by API, transaction journal is searched according to the Transaction Identifier in this amendment order, and described nodename is added in the effective transaction journal found, and search nodal community status information table according to the nodename in this amendment order, from nodal community status information table, obtain the data record meeting filtercondition, update described data record one by one by described data to be updated.Application the embodiment of the present application can meet the Operating Complexity of OLTP, and the demand rapidly inputting/exporting, it is achieved the data record modification on multiple nodes that an office relates to, it is ensured that the synchronicity of data modification and integrity；And when affairs lost efficacy, data recovery can be carried out by rolling back action, it is ensured that the integrity of data base.
Those skilled in the art is it can be understood that can add the mode of required general hardware platform by software to the technology in the embodiment of the present invention and realize.Based on such understanding, the part that prior art is contributed by technical scheme in the embodiment of the present invention the most in other words can embody with the form of software product, this computer software product can be stored in storage medium, such as ROM/RAM, magnetic disc, CD etc., including some instructions with so that a computer equipment (can be personal computer, server, or the network equipment etc.) perform each embodiment of the present invention or the method described in some part of embodiment.
Each embodiment in this specification all uses the mode gone forward one by one to describe, and between each embodiment, identical similar part sees mutually, and what each embodiment stressed is the difference with other embodiments.For system embodiment, owing to it is substantially similar to embodiment of the method, so describe is fairly simple, relevant part sees the part of embodiment of the method and illustrates.
Invention described above embodiment, is not intended that limiting the scope of the present invention.Any amendment, equivalent and improvement etc. made within the spirit and principles in the present invention, should be included within the scope of the present invention.
Claims (15)
1. a data-erasure method based on online transaction processing system OLTP, it is characterised in that including:
Reception client, by calling the data-delete command of application programming interface API transmission, comprises Transaction Identifier, nodename and filtercondition in described data-delete command；
Enter synchronization zone, transaction journal is searched according to described Transaction Identifier in described synchronization zone, judge whether described transaction journal is effective transaction journal, when described transaction journal is effective transaction journal, open the issued transaction labelling in described effective transaction journal, and described nodename is added in the effective transaction journal found；
Search nodal community status information table according to nodename, from described nodal community status information table, obtain the data record meeting described filtercondition；
Determine whether that data record is locked by other affairs；
When described data record is not the most by other transactional lock timing, perform to delete one by one the operation of the data record meeting filtercondition, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, return the described operation searching transaction journal according to described Transaction Identifier；
The data record of filtercondition is met described in deleting one by one；
Update the timestamp of described effective transaction journal；
Close the issued transaction labelling of described effective transaction journal；
Exit described synchronization zone；
Receive client and create order by the affairs calling API transmission；
Create order according to described affairs in transaction attributes status information table, generate a new transaction journal, and be that described new transaction journal distributes unique Transaction Identifier；
It is set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
Method the most according to claim 1, it is characterised in that described search after transaction journal according to described Transaction Identifier, also includes:
Judge whether to find described transaction journal；
When not finding described transaction journal, terminate flow process, when finding described transaction journal, it is judged that whether the submission attribute of the described transaction journal found and rollback attribute are and are not carried out；
When judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process.
Method the most according to claim 1, it is characterised in that the data record meeting filtercondition described in described deletion one by one includes:
Described data record is formed queue；
Order extracts a data record from described queue；
When the data record of described extraction is not dirty data, and unmarked for updating and deleting time, then labelling is deleted described data record, and the associated data record of described data record, and physics and is deleted the dirty data of described associated data record；
When the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and physics deletes the associated data record of described data record；
When the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and physics deletes the dirty data of described associated data record.
Method the most according to claim 3, it is characterised in that also include:
After completing to meet described in deleting one by one the data record of filtercondition, the affairs performing data deletion submit operation to；Or, the data record after deleting is carried out rolling back action.
Method the most according to claim 4, it is characterised in that described affairs submit to operation to include:
Receive client by calling the Transaction Identifier of application programming interface API transmission；
The transaction journal of correspondence is found according to described Transaction Identifier；
When finding effective transaction journal, the submission attribute of described transaction journal is set to executed；
Delete the data record of locking, and the associated data record of described data record；
Described transaction journal is deleted from described transaction attributes status information table.
Method the most according to claim 4, it is characterised in that described rolling back action includes:
Receive client by calling the Transaction Identifier of application programming interface API transmission；
The transaction journal of correspondence is found according to described Transaction Identifier；
When finding effective transaction journal, the rollback attribute of described transaction journal is set to executed；
Release the locking to described data record, and the locking of the associated data record of described data record；
Described transaction journal is deleted from described transaction attributes status information table.
7. a data deletion system based on OLTP, it is characterised in that including: graphic data base server and client side,
Described client, for the API by calling graphic data base server, to described graphic data base server transmission data delete command, comprises Transaction Identifier, nodename and filtercondition in described data-delete command；It is additionally operable to the API by calling graphic data base server, creates order to described graphic data base server transport affairs；
nullDescribed graphic data base server，For entering synchronization zone，Transaction journal is searched according to described Transaction Identifier in described synchronization zone，Judge whether described transaction journal is effective transaction journal，When described transaction journal is effective transaction journal，Open the issued transaction labelling in described effective transaction journal，And described nodename is added in the effective transaction journal found，Nodal community status information table is searched according to nodename，The data record meeting described filtercondition is obtained from described nodal community status information table，Determine whether that data record is locked by other affairs，When described data record is not the most by other transactional lock timing，Perform to delete one by one the operation of the data record meeting filtercondition，Otherwise，When determining affairs corresponding to described transaction journal not less than preset time threshold，Return the described operation searching transaction journal according to described Transaction Identifier，The data record of filtercondition is met described in deleting one by one，Update the timestamp of described effective transaction journal，Close the issued transaction labelling of described effective transaction journal，Exit described synchronization zone；It is additionally operable to create order according to described affairs in transaction attributes status information table, generates a new transaction journal, and be that described new transaction journal distributes unique Transaction Identifier, be set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
System the most according to claim 7, it is characterised in that
Described graphic data base server, it is additionally operable to judge whether to find described transaction journal, when not finding described transaction journal, terminate flow process, when finding described transaction journal, judge whether submission attribute and the rollback attribute of the described transaction journal found are and are not carried out, when judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, flow process is terminated.
System the most according to claim 7, it is characterised in that
Described graphic data base server, after being additionally operable to meet described in deleting one by one the data record of filtercondition, the affairs performing data deletion submit operation to, or the data record after deleting is carried out rolling back action.
10. a graphic data base server, it is characterised in that including:
Receive unit, be used for the data-delete command receiving client by calling the transmission of application programming interface API, described data-delete command comprises Transaction Identifier, nodename and filtercondition；It is additionally operable to receive client and creates order by the affairs calling API transmission；
Search unit, for entering synchronization zone, transaction journal is searched according to described Transaction Identifier in described synchronization zone, judge whether described transaction journal is effective transaction journal, when described transaction journal is effective transaction journal, open the issued transaction labelling in described effective transaction journal, and described nodename is added in the effective transaction journal found；
Acquiring unit, for searching nodal community status information table according to nodename, obtains the data record meeting described filtercondition from described nodal community status information table；
Second judging unit, is used for determining whether that data record is locked by other affairs；
Second performance element, for when described data record is the most by the timing of other transactional lock, triggers and deletes unit and perform operation, otherwise, when determining affairs corresponding to described transaction journal not less than preset time threshold, returns described lookup unit and performs operation；
Delete unit, for meeting the data record of filtercondition described in deletion one by one, update the timestamp of described effective transaction journal, close the issued transaction labelling of described effective transaction journal, exit described synchronization zone；
Also include:
Signal generating unit, generates a new transaction journal in transaction attributes status information table for creating order according to described affairs, and is that described new transaction journal distributes unique Transaction Identifier；
Unit is set, for being set to be not carried out by submission attribute and the rollback attribute of described transaction journal.
11. servers according to claim 10, it is characterised in that also include:
First judging unit, is used for judging whether to find described transaction journal；
First performance element, for when not finding described transaction journal, terminates flow process；
Described first judging unit, is additionally operable to when finding described transaction journal, it is judged that whether the submission attribute of the described transaction journal found and rollback attribute are and are not carried out；
Described first performance element, be additionally operable to when judge to be not carried out time, determine described in the transaction journal that finds be effective transaction journal, perform described described nodename to add the operation in the effective transaction journal found to, otherwise, terminate flow process.
12. servers according to claim 11, it is characterised in that described deletion unit includes:
Queue signal generating unit, forms queue by described data record；
Record extraction unit, order extracts a data record from described queue；
Labelling deletes unit, for not being dirty data when the data record of described extraction, and unmarked for updating and deleting time, then labelling is deleted described data record, and the associated data record of described data record, and physics and is deleted the dirty data of described associated data record；
Described labelling deletes unit, is additionally operable to when the data of described extraction are recorded as dirty data, and when being newly inserted data record, then physics deletes described data record, and physics deletes the associated data record of described data record；
Described labelling deletes unit, it is additionally operable to when the data record of described extraction is not dirty data, unmarked for deleting, and when having been labeled as updating, then physics deletes described data transcript record, labelling deletes the associated data record of described data record, and physics deletes the dirty data of described associated data record.
13. servers according to claim 11, it is characterised in that also include:
Submit unit to, after be used for meeting described in deleting one by one the data record of filtercondition, perform the affairs of data deletion and submit to and operate；
Rollback unit, for carrying out rolling back action to the data record after deleting.
14. servers according to claim 13, it is characterised in that described submission unit includes:
Mark receives unit, receives client by calling the Transaction Identifier of application programming interface API transmission；
Record search unit, finds the transaction journal of correspondence according to described Transaction Identifier；
Attribute arranges unit, when finding effective transaction journal, the submission attribute of described transaction journal is set to executed；
Unit deleted in record, for deleting the data record of locking, and the associated data record of described data record, described transaction journal is deleted from described transaction attributes status information table.
15. servers according to claim 13, it is characterised in that described rollback unit includes:
Mark receives unit, for receiving client by calling the Transaction Identifier of application programming interface API transmission；
Record search unit, for finding the transaction journal of correspondence according to described Transaction Identifier；
Attribute arranges unit, for when finding effective transaction journal, the rollback attribute of described transaction journal is set to executed；
Latch-release unit, for releasing the locking to described data record, and the locking of the associated data record of described data record；
Unit deleted in record, for described transaction journal being deleted from described transaction attributes status information table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110074497.8A CN102103642B (en) | 2011-03-25 | 2011-03-25 | Data-erasure method based on OLTP, system and graphic data base server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110074497.8A CN102103642B (en) | 2011-03-25 | 2011-03-25 | Data-erasure method based on OLTP, system and graphic data base server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102103642A CN102103642A (en) | 2011-06-22 |
| CN102103642B true CN102103642B (en) | 2016-08-03 |
Family
ID=44156412
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110074497.8A Active CN102103642B (en) | 2011-03-25 | 2011-03-25 | Data-erasure method based on OLTP, system and graphic data base server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102103642B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013250625A (en) * | 2012-05-30 | 2013-12-12 | Oki Electric Ind Co Ltd | Business form input system and business form input method |
| CN103473119A (en) * | 2012-06-06 | 2013-12-25 | 百度在线网络技术（北京）有限公司 | Task cooperation device and method |
| CN104243438B (en) * | 2013-06-24 | 2017-08-08 | 阿里巴巴集团控股有限公司 | A kind of db transaction processing method and server |
| US9430274B2 (en) * | 2014-03-28 | 2016-08-30 | Futurewei Technologies, Inc. | Efficient methods and systems for consistent read in record-based multi-version concurrency control |
| CA2991128C (en) * | 2015-07-10 | 2021-03-09 | Ab Initio Technology Llc | Method and architecture for providing database access control in a network with a distributed database system |
| CN108073596B (en) * | 2016-11-10 | 2020-08-14 | 北京国双科技有限公司 | Data deletion method and device for OLAP database |
| CN108228617A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | Ensure the method and device of database manipulation atomicity |
| CN109101368B (en) * | 2018-08-20 | 2022-04-22 | 郑州云海信息技术有限公司 | Data processing method and device |
| CN109559398A (en) * | 2018-12-08 | 2019-04-02 | 宁波博太科智能科技有限公司 | A kind of receipts record processing method |
| CN111897490B (en) * | 2020-07-08 | 2024-06-11 | 阿里巴巴集团控股有限公司 | Method and device for deleting data |
| CN112148712A (en) * | 2020-09-27 | 2020-12-29 | 上海依图网络科技有限公司 | Data processing method, device, equipment and medium |
| CN112667375A (en) * | 2020-12-22 | 2021-04-16 | 杭州东信北邮信息技术有限公司 | Task scheduling method and system based on big data service |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1507597A (en) * | 2001-05-15 | 2004-06-23 | �Ҵ���˾ | Method for managing distributed savepoints across multiple DBMS's within a distributed transaction |
| CN101127045A (en) * | 2007-09-25 | 2008-02-20 | 中兴通讯股份有限公司 | Database repeatable reading implement method, device and database management system |
| CN101615203A (en) * | 2009-07-23 | 2009-12-30 | 中兴通讯股份有限公司 | Concurrency control method and device |
| CN101699439A (en) * | 2009-11-16 | 2010-04-28 | 中兴通讯股份有限公司 | Database transaction submitting method and device |
-
2011
- 2011-03-25 CN CN201110074497.8A patent/CN102103642B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1507597A (en) * | 2001-05-15 | 2004-06-23 | �Ҵ���˾ | Method for managing distributed savepoints across multiple DBMS's within a distributed transaction |
| CN101127045A (en) * | 2007-09-25 | 2008-02-20 | 中兴通讯股份有限公司 | Database repeatable reading implement method, device and database management system |
| CN101615203A (en) * | 2009-07-23 | 2009-12-30 | 中兴通讯股份有限公司 | Concurrency control method and device |
| CN101699439A (en) * | 2009-11-16 | 2010-04-28 | 中兴通讯股份有限公司 | Database transaction submitting method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102103642A (en) | 2011-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102103642B (en) | Data-erasure method based on OLTP, system and graphic data base server | |
| CN102193991B (en) | OLTP(on-line transaction processing)-based data modifying method and system as well as graphic database server | |
| US10678808B2 (en) | Eager replication of uncommitted transactions | |
| CN104793988B (en) | The implementation method and device of integration across database distributed transaction | |
| EP3120261B1 (en) | Dependency-aware transaction batching for data replication | |
| US7769714B2 (en) | Automatic error correction for replication and instantaneous instantiation | |
| US10250693B2 (en) | Idempotence for database transactions | |
| US9830372B2 (en) | Scalable coordination aware static partitioning for database replication | |
| EP1877906B1 (en) | Maintenance of link level consistency between database and file system | |
| KR20210135477A (en) | Systems and methods for augmenting database applications with blockchain technology | |
| US8639677B2 (en) | Database replication techniques for maintaining original linear request order for asynchronous transactional events | |
| CN110196856B (en) | Distributed data reading method and device | |
| JP2023546249A (en) | Transaction processing methods, devices, computer equipment and computer programs | |
| WO2019223228A1 (en) | Data synchronization method and apparatus for distributed heterogeneous database | |
| US11681683B2 (en) | Transaction compensation for single phase resources | |
| US20120330890A1 (en) | Propagating tables while preserving cyclic foreign key relationships | |
| JP2001051879A (en) | Method and system for improved access to nonrelational database | |
| CN105786595B (en) | A kind of transaction control method that two-part is submitted | |
| CN106503257A (en) | Distributed transaction server method and system based on binlog compensation mechanism | |
| CN102317913A (en) | Transaction recovery method and apparatus | |
| US7752225B2 (en) | Replication and mapping mechanism for recreating memory durations | |
| CN102193987B (en) | Method and system for increasing node data relationship based on OLTP (online transaction processing) | |
| US20160019121A1 (en) | Data transfers between cluster instances with delayed log file flush | |
| CN112800060A (en) | Data processing method and device, computer readable storage medium and electronic equipment | |
| US7051051B1 (en) | Recovering from failed operations in a database system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: BEIJING CENTURY BROADBAND INTERNET DATA CENTER CO. Free format text: FORMER OWNER: BEIJING BANYANO DATA CENTER SOLUTIONS LTD. Effective date: 20120919 Free format text: FORMER OWNER: BEIJING CLOUDEX SOFTWARE SERVICES CO., LTD. Effective date: 20120919 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20120919 Address after: 100015, No. 5, building 1, 3 East Road, Jiuxianqiao Road, Beijing, Chaoyang District Applicant after: Beijing Century Broadband Internet Data Center Co., Ltd. Address before: 100015 No. 3, building 5, building 1, Jiuxianqiao East Road, Chaoyang District, Beijing Applicant before: Beijing BANYANO Data Center Solutions Ltd. Applicant before: Beijing CloudEx Software Service Co., Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |