CN115129733A - Method, device and equipment for recording and inquiring bank data change history - Google Patents
Method, device and equipment for recording and inquiring bank data change history Download PDFInfo
- Publication number
- CN115129733A CN115129733A CN202210762834.0A CN202210762834A CN115129733A CN 115129733 A CN115129733 A CN 115129733A CN 202210762834 A CN202210762834 A CN 202210762834A CN 115129733 A CN115129733 A CN 115129733A
- Authority
- CN
- China
- Prior art keywords
- version
- data
- history
- history table
- service information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- General Business, Economics & Management (AREA)
- Technology Law (AREA)
- Strategic Management (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a device and equipment for recording and inquiring bank data change history, which can be applied to the field of big data and the field of finance, can effectively improve the recording and inquiring effect of the bank data change history, and reduce the occupied storage space. The method comprises the following steps: firstly, creating a version history table; the version history table is used for recording the change history of the current business object, then determining the business information table with data change, and adding a set of history table for the business information table; the historical table is consistent with the service information table in structure, and then, according to the type of data change, the service information table and the data in the historical table are correspondingly processed to obtain an updated service information table and an updated historical table; and further, the version time points of the target service object and the specified version number can be inquired through the version history table, the updated service information table and the history table, so that the historical data of the specified version can be obtained.
Description
Technical Field
The application relates to the technical field of big data, in particular to a method, a device and equipment for recording and inquiring bank data change history.
Background
With the rapid development of social economy, each large bank serves as a financial service center, more and more customers handle various financial services through the bank, and the bank needs to process more and more business data.
At present, a bank usually has a history of record change for the change of important business data and parameter data in an IT system, and can trace and inquire the appeal of a history version; when the business data volume is large, the correlation among the business data is complex and the change is frequent, the requirements are met, version backup is often needed to be carried out on the whole business data according to time points, the data volume is large, a large amount of system resources and time are consumed by one-time backup, and a large amount of storage space is also occupied for storing the historical version, so that the existing recording and query method for the data change history of the bank has the disadvantages that the operation is complex, the recorded data volume is large and the efficiency is low when the record of the change history is carried out under the conditions of complex data correlation and large data volume.
Disclosure of Invention
The embodiment of the application mainly aims to provide a method, a device and equipment for recording and querying bank data change history, which can effectively improve the recording and querying effects of the bank data change history and reduce the occupied storage space.
In a first aspect, an embodiment of the present application provides a method for recording and querying a bank data change history, where the method includes:
newly building a version history table; the version history table is used for recording the change history of the current business object;
determining a service information table with data change, and adding a set of history table for the service information table; the historical table is consistent with the service information table in structure;
according to the type of the data change, correspondingly processing the data in the service information table and the history table to obtain an updated service information table and a history table;
and inquiring the version time points of the target service object and the designated version number through the version history table, the updated service information table and the history table to obtain the historical data of the designated version.
Optionally, the version creation time is recorded in both the version history table and the history table.
Optionally, the data change includes at least one of adding data, maintaining data, and deleting data.
Optionally, the querying, through the version history table, the updated service information table, and the history table, the version time points of the target service object and the specified version number to obtain the historical data of the specified version includes:
inquiring whether data with version creation time not larger than the version time point exists in the service table, if so, indicating that part of the data is generated by the current version or is generated before and continues to the version time point and is not modified;
inquiring the closest data of which the version creation time is not more than the version time point in the history table;
and merging the data inquired from the service table and the history table to obtain the history data of the specified version.
In a second aspect, an embodiment of the present application further provides a device for recording and querying a bank data change history, where the device includes:
a new building unit for building a version history table; the version history table is used for recording the change history of the current business object;
the determining unit is used for determining a service information table with data change and adding a set of history table for the service information table; the historical table is consistent with the service information table in structure;
the processing unit is used for correspondingly processing the data in the service information table and the history table according to the type of the data change to obtain an updated service information table and an updated history table;
and the query unit is used for querying the version time points of the target service object and the specified version number through the version history table, the updated service information table and the history table to obtain the historical data of the specified version.
Optionally, the version history table and the history table both record version creation time.
Optionally, the data change includes at least one of adding data, maintaining data, and deleting data.
Optionally, the query unit includes:
the first query subunit is used for querying whether data of which the version creation time is not greater than the version time point exists in the service table, and if so, the data indicate that part of the data is generated by the current version or is not modified again when the data are generated before and continue to the version time point;
the second query subunit is used for querying the closest data of which the version creation time is not more than the version time point in the history table;
and the merging subunit is used for merging the data inquired from the service table and the history table to obtain the history data of the specified version.
The embodiment of the present application further provides a device for recording and querying a bank data change history, including: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is used for storing one or more programs, and the one or more programs comprise instructions which when executed by the processor cause the processor to execute any one implementation mode of the method for recording and querying the bank data change history.
The embodiment of the application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are run on a terminal device, the terminal device is enabled to execute any implementation manner of the method for recording and querying the bank data change history.
The embodiment of the application provides a method, a device and equipment for recording and querying a bank data change history, and the method comprises the steps of firstly creating a version history table; the version history table is used for recording the change history of the current business object, then determining the business information table with data change, and adding a set of history table for the business information table; the history table and the service information table are consistent in structure, and then, according to the type of data change, corresponding processing is carried out on the service information table and data in the history table to obtain an updated service information table and an updated history table; and then, the version history table, the updated service information table and the updated history table can be used for inquiring the version time point of the target service object and the specified version number to obtain the historical data of the specified version, so that the record and the inquiry effect of the bank data change history can be effectively improved, and the occupied storage space is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for recording and querying a bank data change history according to an embodiment of the present application;
FIG. 2 is a diagram of a version history table provided in an embodiment of the present application;
FIG. 3 is a schematic diagram of a history table provided by an embodiment of the present application;
fig. 4 is a schematic composition diagram of a device for recording and querying a bank data change history according to an embodiment of the present application.
Detailed Description
At present, a bank usually has a history of record change for the change of important business data and parameter data in an IT system, and can trace and inquire the appeal of a history version; when the business data volume is large, the association between the business data is complex and the change is frequent, version backup is often required to be performed on the whole business data according to time points to meet the requirements, the data volume is large, a large amount of system resources and time are consumed by one-time backup, and a large amount of storage space is also occupied for storing historical versions.
For example, the following steps are carried out: the database of a financial system contains product information, wherein the number of basic products is 20W, the number of product components is 1000, the number of product conditions is 2W, the basic products are formed by combining a plurality of product components, and on average, one basic product comprises 100 product components; the product components are formed by combining product conditions, and on average, one product component comprises 20 product conditions; the basic product information comprises a basic product main table (with attributes such as basic product name, state, purpose, definition, range and the like) and an association relation table of the basic product and the product components; based on business requirements, a historical version is recorded every time basic product information is changed, and a system needs to support checking basic product information of a specified version time point (such as checking the name of a basic product, which components are associated with the basic product, and which conditions are associated with the components); the existing method solves the problem:
(1) when basic product information is changed every time, the information of a basic product main table, the association with product components, the association between components and conditions, the component information and the data of the condition information before the change time are stored, and the data quantity to be stored is estimated as follows: 1+100+100 × 20 ═ 2100 strips;
(2) if the product component is changed, all information of the basic product containing the component is required to be recorded as version history, the data volume is N (1), and N is the number of basic products containing the changed product component;
(3) if the product condition is changed, the component including the condition and the basic product information including the corresponding component need to be recorded as a version history, the data size is M (2), and M is the number of product components including the change.
Therefore, the existing recording and querying method for the data change history of the bank has the problems that the operation is complex, the recorded data volume is large and the efficiency is low when the record of the change history is made under the conditions of complex data association relation and large data volume, so that how to improve the recording and querying effects of the bank data change history and reduce the occupied storage space is an urgent need to solve at present.
In order to solve the above-mentioned defects, the embodiment of the present application provides a method for recording and querying a bank data change history, first creating a version history table; the version history table is used for recording the change history of the current business object, then determining the business information table with data change, and adding a set of history table for the business information table; the historical table is consistent with the service information table in structure, and then, according to the type of data change, the service information table and the data in the historical table are correspondingly processed to obtain an updated service information table and an updated historical table; and then through the version history table, the updated service information table and the history table, the version time point of the target service object and the specified version number is inquired to obtain the historical data of the specified version, so that the record and the inquiry effect of the bank data change history can be effectively improved, and the occupied storage space is reduced.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
First embodiment
Referring to fig. 1, a schematic flow chart of a method for recording and querying a bank data change history provided in this embodiment is shown, where the method includes the following steps:
s101: newly building a version history table; the version history table is used for recording the change history of the current business object.
In the embodiment, in order to effectively improve the recording and querying effects of the bank data change history and reduce the occupied storage space, the application proposes that the time stamp when the data change occurs and the changed data (before the change and after the change) are recorded, the time based on the whole system is the same and is always increased (the time cannot be returned), that is, when the changed history version is traced every time (the change is taken as a primary version), the query can be traced quickly through the time stamp of the current version and the history record of the data, and because only the changed data is recorded every time instead of the whole data being backed up according to the time, the occupied storage space is naturally less, and the efficiency is more efficient.
Specifically, a new version history table (version _ history) is first required, as shown in fig. 2, to perform the subsequent step S104. The VERSION history table is used for recording the change history of the current business OBJECT, the business OBJECT refers to a main body of change information, for example, basic product information is modified, the modified basic product is the main body to be recorded in the VERSION history, each business OBJECT has own ID, namely, OBJECT _ ID, VERSION _ CREATETIME is the date and time of VERSION creation, which is the date and time of completion of change, and the date and time should have monotone increment and consistency in the system and cannot be backed; other fields can also be added with auxiliary fields, such as OBJECT _ TYPE, classification of business OBJECTs, such as 01-basic product, 02-product component, and the like; VERSION NO, giving a number, e.g. starting with 00001.
S102: determining a service information table with data change, and adding a set of history table for the service information table; wherein, the history table is consistent with the service information table structure.
In this embodiment, in order to effectively improve the recording and querying effects of the bank data change history and reduce the occupied storage space, it is further necessary to determine a service information table in which data change occurs, and add a set of history table (xxxx _ history) to the service information table; the history table and the service information table have the same structure, but a DATA _ CREATETIME field needs to be added to the history table to be used as a part of key values, DATA _ CREATETIME is DATA creation date, the field is consistent with VERSION _ CREATETIME of the VERSION history table, and the value of the field is not modified any more after DATA is inserted into xxxx _ history; for example, the basic product main table is basic _ product, the history table is basic _ product _ history, and the schematic structural diagram is shown in fig. 3, where the DATA enclosed by the block is DATA _ CREATETIME (DATA creation date).
S103: and according to the type of the data change, correspondingly processing the data in the service information table and the history table to obtain an updated service information table and the updated history table.
In this embodiment, after determining the service information table with the data change through step S102, and adding a set of history table to the service information table, further, according to the type of the data change, corresponding processing may be performed on the service information table and the data in the history table to obtain an updated service information table and history table, so as to execute subsequent step S104.
Wherein the data change includes at least one of adding data, maintaining data, and deleting data.
Specifically, when data is added newly, for example, a new basic product and a new product component are created, version _ history is inserted into a version record, a service table is added with service data conventionally, and a corresponding history table is not inserted and updated. When data is maintained, for example, basic product associated component information is maintained, version _ history is inserted into a version record, values of the service table related to updated data before updating are inserted into a corresponding history table, and then updating is performed according to the conventional method. It should be noted that, the present application does not support physical deletion of data, and data processing data deletion of an important service system is a manner in which an account is deleted logically, and a specific logical deletion of a change flow is the same as the foregoing data maintenance flow, which is not described again.
S104: and inquiring version time points of the target service object and the specified version number through the version history table, the updated service information table and the history table to obtain historical data of the specified version.
In this embodiment, when querying the latest data, only the service information table needs to be queried, because the latest data is all embodied in the original service table, so that the service table needs to be looked up according to the conventional method for looking up the current latest data.
When the historical data of the designated version is queried, the version time points of the target business object and the designated version number are queried through the version historical table, the updated business information table and the historical table to obtain the historical data of the designated version.
Specifically, an alternative implementation is to first query the service table whether there is data in the service table whose version creation time is not greater than the version time point, and if so, it indicates that part of the data is generated for the current version or has not been modified until the version time point since the previous generation. Then, the most recent data in the history table whose version creation time is not greater than the version timepoint is queried. Then, the data searched from the service table and the history table are merged to obtain the history data of the specified version.
Thus, by executing the steps S101-S104, the method for realizing the historical record and query of the associated data established based on the timestamp transmission consistency is simpler in process, less in data volume to be recorded and higher in efficiency.
In summary, in the method for recording and querying the bank data change history provided by this embodiment, a version history table is created at first; the version history table is used for recording the change history of the current business object, then determining the business information table with data change, and adding a set of history table for the business information table; the historical table is consistent with the service information table in structure, and then, according to the type of data change, the service information table and the data in the historical table are correspondingly processed to obtain an updated service information table and an updated historical table; and then through the version history table, the updated service information table and the history table, the version time point of the target service object and the specified version number is inquired to obtain the historical data of the specified version, so that the record and the inquiry effect of the bank data change history can be effectively improved, and the occupied storage space is reduced.
Second embodiment
In this embodiment, a device for recording and querying a bank data change history will be described, and please refer to the above method embodiment for related content.
Referring to fig. 4, a schematic composition diagram of a device for recording and querying a bank data change history provided in this embodiment specifically includes:
a new creating unit 401, configured to create a new version history table; the version history table is used for recording the change history of the current business object;
a determining unit 402, configured to determine a service information table with data change, and add a set of history table to the service information table; the historical table is consistent with the service information table in structure;
a processing unit 403, configured to perform corresponding processing on the data in the service information table and the history table according to the type of the data change, so as to obtain an updated service information table and updated history table;
the query unit 404 is configured to query the version time points of the target service object and the specified version number through the version history table and the updated service information table and history table, so as to obtain historical data of the specified version.
In an implementation manner of this embodiment, the version history table and the history table each record a version creation time.
In one implementation of this embodiment, the data change includes at least one of adding data, maintaining data, and deleting data.
In an implementation manner of this embodiment, the querying unit 404 includes:
the first query subunit is used for querying whether data of which the version creation time is not greater than the version time point exists in the service table, and if so, the data indicate that part of the data is generated by the current version or is not modified again when the data are generated before and continue to the version time point;
the second query subunit is used for querying the closest data of which the version creation time is not more than the version time point in the history table;
and the merging subunit is used for merging the data inquired from the service table and the history table to obtain the history data of the specified version.
In summary, in the device for recording and querying the bank data change history provided by this embodiment, a version history table is created at first; the version history table is used for recording the change history of the current business object, then determining the business information table with data change, and adding a set of history table for the business information table; the historical table is consistent with the service information table in structure, and then, according to the type of data change, the service information table and the data in the historical table are correspondingly processed to obtain an updated service information table and an updated historical table; and then through the version history table, the updated service information table and the history table, the version time point of the target service object and the specified version number is inquired to obtain the historical data of the specified version, so that the record and the inquiry effect of the bank data change history can be effectively improved, and the occupied storage space is reduced.
Further, an embodiment of the present application further provides a device for recording and querying a bank data change history, including: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is used for storing one or more programs, and the one or more programs comprise instructions which when executed by the processor cause the processor to execute any one of the implementation methods of the method for recording and querying the bank data change history.
Further, an embodiment of the present application further provides a computer-readable storage medium, where an instruction is stored in the computer-readable storage medium, and when the instruction runs on a terminal device, the terminal device is caused to execute any implementation method of the above method for recording and querying a bank data change history.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a media gateway, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.
It should be noted that, in the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In addition, the method, the device and the equipment for recording and inquiring the bank data change history provided by the invention can be applied to the field of big data and the field of finance. The above is merely an example, and the application fields of the method, the apparatus and the device for recording and querying the bank data change history provided by the present invention are not limited.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for recording and inquiring bank data change history, which is characterized by comprising the following steps:
newly building a version history table; the version history table is used for recording the change history of the current business object;
determining a service information table with data change, and adding a set of history table for the service information table; the historical table is consistent with the service information table in structure;
according to the type of the data change, correspondingly processing the data in the service information table and the history table to obtain an updated service information table and a history table;
and inquiring the version time points of the target service object and the designated version number through the version history table, the updated service information table and the history table to obtain the historical data of the designated version.
2. The method of claim 1, wherein a version creation time is recorded in both the version history table and the history table.
3. The method of claim 1, wherein the data change comprises at least one of adding data, maintaining data, and deleting data.
4. The method according to any one of claims 1 to 3, wherein the obtaining of the historical data of the specified version by querying version time points of the target business object and the specified version number through the version history table, the updated business information table and the history table comprises:
inquiring whether data with version creation time not larger than the version time point exists in the service table, if so, indicating that part of the data is generated by the current version or is generated before and continues to the version time point and is not modified;
querying the closest data of which the version creation time is not more than the version time point in the history table;
and merging the data inquired from the service table and the history table to obtain the history data of the specified version.
5. An apparatus for recording and querying a history of changes to bank data, the apparatus comprising:
a new building unit for building a version history table; the version history table is used for recording the change history of the current business object;
the determining unit is used for determining a service information table with data change and adding a set of history table for the service information table; the historical table and the service information table have the same structure;
the processing unit is used for correspondingly processing the data in the service information table and the history table according to the type of the data change to obtain an updated service information table and an updated history table;
and the query unit is used for querying the version time points of the target service object and the specified version number through the version history table, the updated service information table and the history table to obtain the historical data of the specified version.
6. The apparatus of claim 5, wherein a version creation time is recorded in each of the version history table and the history table.
7. The apparatus of claim 5, wherein the data change comprises at least one of adding data, maintaining data, and deleting data.
8. The apparatus according to any one of claims 5-7, wherein the query unit comprises:
the first query subunit is used for querying whether data of which the version creation time is not greater than the version time point exists in the service table, if so, the data indicate that part of the data is generated by the current version or is generated before and continues to the version time point and is not modified;
the second query subunit is used for querying the closest data of which the version creation time is not more than the version time point in the history table;
and the merging subunit is used for merging the data inquired from the service table and the history table to obtain the history data of the specified version.
9. A device for recording and querying bank data change history, which is characterized by comprising: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is to store one or more programs, the one or more programs comprising instructions, which when executed by the processor, cause the processor to perform the method of any of claims 1-4.
10. A computer-readable storage medium having stored therein instructions that, when executed on a terminal device, cause the terminal device to perform the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210762834.0A CN115129733A (en) | 2022-06-30 | 2022-06-30 | Method, device and equipment for recording and inquiring bank data change history |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210762834.0A CN115129733A (en) | 2022-06-30 | 2022-06-30 | Method, device and equipment for recording and inquiring bank data change history |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115129733A true CN115129733A (en) | 2022-09-30 |
Family
ID=83380995
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210762834.0A Pending CN115129733A (en) | 2022-06-30 | 2022-06-30 | Method, device and equipment for recording and inquiring bank data change history |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115129733A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116483873A (en) * | 2023-06-25 | 2023-07-25 | 云筑信息科技(成都)有限公司 | Method for realizing historical snapshot data query based on change data |
-
2022
- 2022-06-30 CN CN202210762834.0A patent/CN115129733A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116483873A (en) * | 2023-06-25 | 2023-07-25 | 云筑信息科技(成都)有限公司 | Method for realizing historical snapshot data query based on change data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11288002B2 (en) | System and method for providing high availability data | |
| CN109299157B (en) | Data export method and device for distributed big single table | |
| US20210049073A1 (en) | Summary file change log for faster forever incremental backup | |
| CN115129733A (en) | Method, device and equipment for recording and inquiring bank data change history | |
| CN113239012B (en) | Database migration method and device, electronic equipment and storage medium | |
| CN112783887A (en) | Data processing method and device based on data warehouse | |
| CN115357622A (en) | Service processing method based on hotspot data and server | |
| US7213029B2 (en) | Quiescing work bounded by application transactions consisting of multiple relational database transactions | |
| CN114579059A (en) | File data migration method, device, equipment and storage medium | |
| CN109739883B (en) | Method and device for improving data query performance and electronic equipment | |
| CN110597828A (en) | Database changing method, device, equipment and storage medium | |
| CN115203488B (en) | Graph database management method and device and electronic equipment | |
| CN111753141B (en) | Data management method and related equipment | |
| CN115718787B (en) | Data table data synchronization method, query method, electronic device and storage medium | |
| CN114820079B (en) | Crowd determination method, device, equipment and medium | |
| CN117614973B (en) | File storage method based on multi-cloud architecture | |
| CN115374122A (en) | Rollback data migration method, apparatus, device and medium of rollback table space | |
| CN115617801A (en) | Data retrieval method, device, equipment and medium based on distributed system | |
| CN111881091A (en) | Data storage method and device, electronic equipment and storage medium | |
| CN112416465A (en) | Information configuration method and device, electronic equipment and storage medium | |
| CN117112541A (en) | Data management method, device, big data platform and storage medium | |
| CN115757432A (en) | Business data storage method and device, electronic equipment and storage medium | |
| CN115700663A (en) | Data index management system and method based on knowledge graph | |
| CN117149512A (en) | Metadata operation processing method and device | |
| CN115170089A (en) | Service management system for bidding agent service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |