WO2021093462A1 - Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif - Google Patents

Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif Download PDF

Info

Publication number
WO2021093462A1
WO2021093462A1 PCT/CN2020/117005 CN2020117005W WO2021093462A1 WO 2021093462 A1 WO2021093462 A1 WO 2021093462A1 CN 2020117005 W CN2020117005 W CN 2020117005W WO 2021093462 A1 WO2021093462 A1 WO 2021093462A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
block
business attribute
change
hash value
Prior art date
Application number
PCT/CN2020/117005
Other languages
English (en)
Chinese (zh)
Inventor
杨新颖
Original Assignee
蚂蚁区块链科技(上海)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 蚂蚁区块链科技(上海)有限公司 filed Critical 蚂蚁区块链科技(上海)有限公司
Publication of WO2021093462A1 publication Critical patent/WO2021093462A1/fr

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/22—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the embodiments of this specification relate to the field of information technology, and in particular to a method, device, and equipment for storing operation records in a database.
  • the centralized database server When the centralized database server provides external data services, it also needs to save the user's operations on the data record (including adding, clearing, hiding, querying, etc.) resulting in the change of the data record or the status change of a certain attribute in the data record , That is, the operation records need to be stored for retrospective or rollback. In a centralized scenario, the number of data records is often huge, and the number of operation records is also often very large.
  • the purpose of the embodiments of the present application is to provide a flexible operation record storage solution in a database.
  • the operation instruction contains a business attribute; evaluate the degree of change of the operation instruction to the data record containing the business attribute, and determine the operation influence characteristic value, wherein the operation influence characteristic value and the operation influence characteristic value include The degree of change of the data record of the business attribute is positively correlated; if the operation influence characteristic value exceeds the threshold, an operation record containing the operation instruction is generated and stored; otherwise, the data record containing the business attribute is determined The change state of, an operation record containing the change state is generated and stored.
  • the embodiment of this specification also provides an operation record storage device in a block chain ledger, including: a receiving module, which receives an operation instruction, the operation instruction contains business attributes; an evaluation module, which evaluates that the operation instruction is effective
  • the change degree of the data record containing the business attribute is determined to determine the operation influence characteristic value, wherein the operation influence characteristic value is positively correlated with the change degree of the data record containing the business attribute; the first storage module, if the If the operation influence characteristic value exceeds the threshold, generate an operation record containing the operation instruction, and store it; the second storage module, otherwise, determine the change state of the data record containing the business attribute, and generate the change state containing the change State operation records and storage.
  • the relevant operation records are dynamically generated to ensure that the data status can be accurately traced back, saving the system overhead when storing the operation records, and realizing a flexible operation record storage method.
  • any one of the embodiments of the present specification does not need to achieve all the above-mentioned effects.
  • Figure 1 is a schematic diagram of the system architecture involved in an embodiment of the specification
  • FIG. 2 is a schematic diagram of the data system architecture provided by an embodiment of this specification.
  • FIG. 3 is a schematic flowchart of a method for storing operation records in a block chain ledger provided by an embodiment of the specification
  • Fig. 4 is a schematic diagram of a process for generating a block chain ledger provided by an embodiment of the specification
  • FIG. 5 is a schematic diagram of a block header of a data block provided by an embodiment of this specification.
  • FIG. 6 is a schematic structural diagram of an operation record storage device in a database provided by an embodiment of this specification.
  • Fig. 7 is a schematic structural diagram of a device for configuring the method of the embodiment of this specification.
  • FIG. 1 is a schematic diagram of a system architecture involved in an embodiment of the specification.
  • an enterprise organization can face multiple users, and each user can query the database service provider through its corresponding enterprise organization.
  • the organization connected to the database server is a financial product company, and the data records can be individual users’ financial management records in the financial product company; or, the connected organization can be a government department, where the data records are what the government department has for the department. Expense details of the managed public project; or, the database server is connected to a hospital, and the data record is the patient’s medical record; or the database server is connected to a third-party payment agency, and the data record can be an individual user Payment records through the agency, and so on.
  • FIG. 2 is a schematic diagram of the data system architecture provided by the embodiment of the present specification.
  • the user's data is stored in the main body of the ledger shown in Figure 2 (it can be a relational table, a blockchain ledger, etc.).
  • the index can be defined as needed.
  • the index can include an inverted index with the business attribute of the data record as the main key, and the block height and offset sequence number as the value; the metadata part can be Perform statistics on the main body, index and other information of the ledger to obtain relevant information.
  • the metadata part can include: the total number of data records in the ledger, the total number of data blocks in the ledger, the total number of business attributes in the ledger, and the quantity The number of data records of the top business attributes, the number of data blocks where a business attribute is located in the ledger, and so on.
  • metadata can also perform state calculations for certain business attributes.
  • the data record is about the user's expenditure/income record, or the user's purchase/sale of securities Records and so on.
  • the metadata can also include world state values for certain business attributes (for example, the user's amount of money).
  • the user can also perform various operations on the data record in the ledger, for example, including updating UPDATA, adding APPEND, clearing PURGE, verifying VERIFY, querying SELECT, hiding OCCULT, and so on.
  • corresponding operation records will be generated, and the operation records can be stored in the log part or the main part of the ledger in the storage.
  • the embodiment of this specification also provides a method for storing operation records in a block chain ledger, as shown in FIG. 3, which is the flow of the method for storing operation records in a block chain ledger provided by the embodiment of this specification. Schematic diagram, including the following steps.
  • S301 Receive an operation instruction, where the operation instruction includes a business attribute.
  • operation instructions can use common structured query language (SQL), including such as UPDATA, APPEND, PURGE, VERIFY, SELECT, OCCULT, and so on.
  • SQL structured query language
  • SELECT balance, FULL
  • UPDATA key1, v1, v2
  • the ledger will contain data records with the business attribute "key1" Replace v1 in v2 with v2 and so on.
  • the operating instructions can come from the database server, the docking organization, or the users of the docking organization, and so on.
  • operating instructions can also be user-defined statements with certain functions, such as clear PURGE (used to clear data blocks before the specified block height) in the block chain ledger.
  • Hidden OCCULT used to hide the plaintext of a specified data record
  • Business attributes can be fields related to the user's business data, for example, user ID, mobile phone number, item name, etc. There are no restrictions here; business attributes can also be related to the main body of the ledger, index, and metadata that store user data Fields, such as the name of the ledger, the name of the index, the number of rows and columns in the index, and so on.
  • the degree of impact change here mainly includes “changes to the data record itself”, “changes to the index related to the data record”, and “changes to the metadata” and so on.
  • a query command may not change any data records or metadata
  • a hidden command OCCULT may affect a data record
  • an UPDATA may affect all data records containing specified business attributes, and for Both indexing and metadata may have a corresponding impact.
  • Metadata related to the main body of the ledger can be included. For example, the total number of data records in the ledger, the total number of business attributes in the ledger, and the number of business attribute data records in the top several rankings (for example, the top 20).
  • the number of the top 100 data records containing a certain business attribute is recorded in sequence
  • the business attribute "key1” is in the table
  • the number of data records containing the business attribute "key1” is in the table. If the number is "N1”, it can be known that the operation instruction may affect the "N1" data records.
  • the operation influence characteristic value exceeds the threshold, it indicates that the operation instruction may have affected multiple data records and metadata. If the change status of each data record is recorded in the operation instruction, considerable resources may be required.
  • the generated operation record may also include the receiving time of the operation instruction, the user ID of the specific sending instruction, etc., and the operation instruction is stored in plain text.
  • the generated operation record can be stored in the corresponding log file.
  • the generated operation record can also be written into the data block in the ledger.
  • the operation influence characteristic value does not exceed the threshold, it can indicate that the operation record may only affect a small number of data records. For example, for an operation instruction APPEND (key1, V), only a data record containing the business attribute "key1" is added to the database. In the metadata, the possible change is the data record corresponding to "key1" The number of items is +1, or the possible change is that the world state corresponding to "key1" is changed from the current value to the current value plus the corresponding value in "V".
  • the change of the data record itself may be directly recorded. That is, it is determined that in the data record containing the business attribute that has changed, the initial value and the change value of the business attribute are determined, and the operation record containing the initial value and the change value of the business attribute is generated.
  • the cumulative value of the business attribute has a specific meaning to the user (for example, the account balance caused by the change in user account expenditure and income, the user’s buying or selling Profit value, etc.).
  • the cumulative status value of the business attribute in the data record containing the business attribute can also be determined, and an operation record including the cumulative status value can be generated.
  • one operation instruction will only affect one change of the accumulated state value.
  • the state value of the data record when recording the state value of the data record, it is also possible to record the before and after changes of the data record completely, and record the first data hash value of the data record before the change and the data record after the change.
  • the second data hash value of the data record generates an operation record containing the first data hash value and the second data hash value.
  • both the hash value before the data record change and the original text before the data record change are recorded.
  • the data can also be verified according to the first data hash value of the data record: That is, after the rollback, the rollback hash value of the data record is recalculated and compared with the first data hash value. If it is consistent, the rollback is correct and the correctness of the data rollback is ensured.
  • the second data hash value is used when the data state changes next time, and is used to trace back according to the first data hash value and the second data hash value in the operation record.
  • the operation record before generating the operation record, first evaluate the degree of change that the operation instruction may have on the data record containing the business attribute. If the degree of change is large, record the operation instruction and generate the operation containing the operation instruction Record and store; if the degree of change is not large, record the changed data record or its related hash value, generate an operation record containing the aforementioned state change, and store it.
  • the relevant operation records are dynamically generated, while ensuring that the data status can be accurately traced back, the system overhead when storing the operation records is saved, and a flexible operation record storage method is realized.
  • the database involved in the embodiment of this specification may be a centralized database that provides services to external parties with a blockchain ledger.
  • the blockchain ledger here can be either a blockchain ledger or a centralized blockchain-like ledger.
  • FIG. 4 is a schematic diagram of the process of generating a block chain ledger provided by the embodiment of this specification, including:
  • S401 Receive a data record to be stored, and determine a hash value of each data record, where the data record contains business attributes.
  • the data records to be stored here can be various consumption records of individual users on the client side, or they can be business results, intermediate states, and operations generated when the application server executes business logic based on user instructions. Records and so on. Specific business scenarios can include consumption records, audit logs, supply chains, government supervision records, medical records, and so on.
  • the data record contains business attributes.
  • the business attribute is generally the only one in the docking organization, and the business attributes are based on different
  • the business scenarios of, can include user name, user ID number, driver’s license number, mobile phone number, project unique number, etc.
  • the data record is the user's consumption record
  • the business attribute at this time is the user ID (including mobile phone number, ID number, user name, etc.), or the user ID is hashed
  • the hash value obtained by the algorithm; or, for government agencies, the data record is the overhead flow of multiple public projects, then the business attribute at this time can be a unique number for each project.
  • the business attribute can be stored in a designated field in the data record (for example, the head or tail of the data record), so that the database server and the user can easily obtain the business attribute of the data record from it.
  • multiple data records can be included in the same ledger.
  • the business attributes of these data records are likely to be different. For example, when a ledger is open to multiple users, the data records may come from different users. If the business attribute is a user ID, it is easy to understand that different data records often contain different user IDs.
  • S403 When a preset block forming condition is reached, determine each data record to be written in the data block, and generate an Nth data block including the hash value of the data block and the data record.
  • the preset blocking conditions include: the number of data records to be stored reaches the number threshold, for example, every time one thousand data records are received, a new data block is generated and one thousand data records are written into the block; or , The time interval from the last block formation time reaches the time threshold, for example, every 5 minutes, a new data block is generated, and the data records received within these 5 minutes are written into the block.
  • N refers to the serial number of the data block.
  • the data block is in the form of a block chain, which is arranged sequentially based on the order of the block time, and has strong timing characteristics.
  • the block height of the data block increases monotonically based on the sequence of the block time.
  • the block height can be a sequence number, at this time the block height of the Nth data block is N; the block height can also be generated in other ways.
  • the data block at this time is the initial data block.
  • the current data block (the first data block) can be generated based on the hash value of the previous data block (that is, the N-1th data block). For example, a feasible way is to determine the hash value of each data record to be written in the Nth block, and generate a Merck according to the order in the block.
  • the root hash value of the Merkel tree and the hash value of the previous data block are spliced together, and the hash algorithm is used again to generate the hash value of the current block.
  • the specific verification method includes recalculating the hash value of the data record itself and the hash value of the data block in which it is located, and comparing it with the locally stored hash value.
  • the data block generated in the above manner may include two parts: a block header and a block body.
  • the block body can be used to store the plaintext of the spliced data, or the hash value of the spliced data, etc.;
  • the block header can be used to store metadata about the data block, for example, the version number of the ledger, the hash of the previous data block Value, the root hash value of the Merkel tree composed of the spliced data in the own data block, the hash value of the own data block, the state array used to record the operated state of the spliced data, and so on.
  • FIG. 5 is a schematic diagram of a block header of a data block provided by an embodiment of this specification.
  • the user's data record is stored in the blockchain ledger, and integrity verification can be initiated at any time, thereby ensuring that the user's data will not be tampered with.
  • the blockchain ledger is a broadly defined ledger, which not only includes the part of the structure that stores the user's data record, but also includes the storage of metadata and operations related to the data record. Logs, indexes, and so on.
  • data records are stored in a non-tamperable block chain ledger, but the database server can also check the "status data" of a certain business attribute (including accumulated value, whether it has been operated, the time it has been operated, etc.) Etc.) to calculate.
  • the status data related to the business attribute is recorded in a designated area block in the index table or metadata.
  • the database server can determine the changed designated area block containing the business attribute according to the business attribute, and then determine the first block hash value of the designated area block before the change and the changed Specify the second block of the hash value of the area block, and generate an operation record containing the first block of the hash value and the second block of the hash value.
  • the first block of hash value and the second block of hash value have similar functions to the aforementioned first data hash value and second data hash value, and are used for the rollback and traceability of the specified area block. Ensure the accuracy of data rollback.
  • the generated operation record may also include the position mark of the designated table block and the business attribute for traceability and rollback.
  • an embodiment of this specification also provides an operation record storage device in a database, as shown in FIG. 6, which is a schematic structural diagram of an operation record storage device in a database provided by an embodiment of this specification, including the following modules .
  • the receiving module 601 receives an operation instruction, and the operation instruction includes a business attribute.
  • the evaluation module 603 evaluates the degree of change of the operation instruction to the data record containing the business attribute, and determines the operation influence characteristic value, wherein the operation influence characteristic value and the degree of change of the data record containing the business attribute Positive correlation.
  • the first storage module 605 if the operation influence characteristic value exceeds a threshold, generates an operation record containing the operation instruction, and stores it.
  • the second storage module 607 otherwise, determines the change state of the data record containing the business attribute, generates an operation record containing the change state, and stores it.
  • the evaluation module 603 evaluates the degree of change of the operation instruction to the data record containing the business attribute according to the type of the operation instruction.
  • the evaluation module 603 determines the number of data records containing the business attribute, and evaluates the degree of change of the operation instruction to the data records containing the business attribute according to the number .
  • the second storage module 607 determines that in the changed data record containing the business attribute, the initial value and the changed value of the business attribute are generated to contain the business attribute Or, determine the cumulative status value of the business attribute in the data record containing the business attribute, and generate the operation record containing the cumulative status value.
  • the second storage module 607 determines that among the changed data records containing the business attributes, the first data hash value of the data record before the change and the data record after the change The second data hash value of the data record generates an operation record containing the first data hash value and the second data hash value.
  • the second storage module 607 determines the designated area block containing the business attribute that has changed; and determines that before the change occurs The first block hash value of the designated area block and the second block hash value of the designated area block after the change occurs, and an operation record containing the first block hash value and the second block hash value is generated .
  • the device further includes a data block generation module 609, which receives the data records to be stored and determines the hash value of each data record.
  • the data record contains the business attribute; when the preset block condition is reached, it is determined
  • the setting method is given; when N>1, the hash value of the Nth data block is determined according to the data records in the data block to be written and the hash value of the N-1th data block, and the Nth data block is generated.
  • the hash value of the data block and the Nth data block of each data record wherein the block height of the data block increases monotonically based on the sequence of the block time.
  • the preset blocking condition includes: the number of data records to be stored reaches the number threshold; or, the time interval from the last blocking time reaches the time threshold.
  • the embodiments of this specification also provide a computer device, which includes at least a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the operations shown in FIG. 3 when the program is executed. Record storage prevention and control methods.
  • FIG. 7 shows a more specific hardware structure diagram of a computing device provided by an embodiment of this specification.
  • the device may include a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050.
  • the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 realize the communication connection between each other in the device through the bus 1050.
  • the processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits for execution related Program to realize the technical solutions provided in the embodiments of this specification.
  • a general-purpose CPU Central Processing Unit, central processing unit
  • microprocessor microprocessor
  • application specific integrated circuit Application Specific Integrated Circuit, ASIC
  • ASIC Application Specific Integrated Circuit
  • the memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc.
  • the memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, related program codes are stored in the memory 1020 and called and executed by the processor 1010.
  • the input/output interface 1030 is used to connect an input/output module to realize information input and output.
  • the input/output/module can be configured in the device as a component (not shown in the figure), or it can be connected to the device to provide corresponding functions.
  • the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc.
  • an output device may include a display, a speaker, a vibrator, an indicator light, and the like.
  • the communication interface 1040 is used to connect a communication module (not shown in the figure) to realize the communication interaction between the device and other devices.
  • the communication module can realize communication through wired means (such as USB, network cable, etc.), or through wireless means (such as mobile network, WIFI, Bluetooth, etc.).
  • the bus 1050 includes a path to transmit information between various components of the device (for example, the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040).
  • the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include the equipment necessary for normal operation. Other components.
  • the above-mentioned device may also include only the components necessary to implement the solutions of the embodiments of the present specification, and not necessarily include all the components shown in the figures.
  • the embodiment of this specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the operation record storage method shown in FIG. 3 is implemented.
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • a typical implementation device is a computer.
  • the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game control A console, a tablet computer, a wearable device, or a combination of any of these devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé et un appareil de mémorisation d'un enregistrement d'opération dans une base de données, et un dispositif. Le procédé consiste à : recevoir une instruction d'opération, l'instruction d'opération comprenant un attribut de service (S301) ; évaluer le degré selon lequel l'instruction d'opération modifie un enregistrement de données comprenant l'attribut de service, et déterminer une valeur de caractéristique d'influence d'opération, la valeur de caractéristique d'influence d'opération étant corrélée positivement avec le degré selon lequel est modifié l'enregistrement de données comprenant l'attribut de service (S303) ; si la valeur de caractéristique d'influence d'opération dépasse une valeur seuil, générer et mémoriser un enregistrement d'opération comprenant l'instruction d'opération (S305) ; sinon, déterminer un état de modification de l'enregistrement de données comprenant l'attribut de service, et générer et mémoriser un enregistrement d'opération comprenant l'état de modification (S307).
PCT/CN2020/117005 2019-11-11 2020-09-23 Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif WO2021093462A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911094100.4A CN111046052B (zh) 2019-11-11 2019-11-11 一种数据库中的操作记录存储方法、装置及设备
CN201911094100.4 2019-11-11

Publications (1)

Publication Number Publication Date
WO2021093462A1 true WO2021093462A1 (fr) 2021-05-20

Family

ID=70231903

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117005 WO2021093462A1 (fr) 2019-11-11 2020-09-23 Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif

Country Status (2)

Country Link
CN (1) CN111046052B (fr)
WO (1) WO2021093462A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111046052B (zh) * 2019-11-11 2021-04-06 蚂蚁区块链科技(上海)有限公司 一种数据库中的操作记录存储方法、装置及设备
CN111444215A (zh) * 2020-06-12 2020-07-24 支付宝(杭州)信息技术有限公司 一种块链式账本中的成块方法、装置及设备
US20230409594A1 (en) * 2022-06-15 2023-12-21 International Business Machines Corporation Conditional replication of data

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104715041A (zh) * 2015-03-24 2015-06-17 深圳市乾华数据科技有限公司 一种数据库恢复方法及系统
CN107145403A (zh) * 2017-04-20 2017-09-08 浙江工业大学 面向Web开发环境的关系型数据库数据回溯方法
US20180329931A1 (en) * 2017-05-10 2018-11-15 Dropbox, Inc. Automatically coordinating application schema changes in a distributed data storage system
CN110020547A (zh) * 2019-01-31 2019-07-16 阿里巴巴集团控股有限公司 一种数据隐匿方法、装置及设备
CN110362570A (zh) * 2019-06-20 2019-10-22 阿里巴巴集团控股有限公司 一种数据存储方法、装置及设备
CN111046052A (zh) * 2019-11-11 2020-04-21 支付宝(杭州)信息技术有限公司 一种数据库中的操作记录存储方法、装置及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4697126B2 (ja) * 2006-11-21 2011-06-08 株式会社デンソー 軟判定補正方法、受信装置、プログラム
CN102073555A (zh) * 2009-11-24 2011-05-25 联想(北京)有限公司 一种备份方法、实现备份的装置及计算机
CN110046162B (zh) * 2019-03-26 2023-06-20 创新先进技术有限公司 辅助证据存证方法、系统、装置及设备
CN110275916B (zh) * 2019-05-23 2021-01-12 创新先进技术有限公司 数据操作记录的存储方法、系统、装置及设备
CN110347679B (zh) * 2019-06-20 2020-08-04 阿里巴巴集团控股有限公司 一种基于收据的数据存储方法、装置及设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104715041A (zh) * 2015-03-24 2015-06-17 深圳市乾华数据科技有限公司 一种数据库恢复方法及系统
CN107145403A (zh) * 2017-04-20 2017-09-08 浙江工业大学 面向Web开发环境的关系型数据库数据回溯方法
US20180329931A1 (en) * 2017-05-10 2018-11-15 Dropbox, Inc. Automatically coordinating application schema changes in a distributed data storage system
CN110020547A (zh) * 2019-01-31 2019-07-16 阿里巴巴集团控股有限公司 一种数据隐匿方法、装置及设备
CN110362570A (zh) * 2019-06-20 2019-10-22 阿里巴巴集团控股有限公司 一种数据存储方法、装置及设备
CN111046052A (zh) * 2019-11-11 2020-04-21 支付宝(杭州)信息技术有限公司 一种数据库中的操作记录存储方法、装置及设备

Also Published As

Publication number Publication date
CN111046052B (zh) 2021-04-06
CN111046052A (zh) 2020-04-21

Similar Documents

Publication Publication Date Title
WO2021073242A1 (fr) Procédés, appareil et dispositif de création d'index et d'interrogation de données
US10255108B2 (en) Parallel execution of blockchain transactions
WO2021093462A1 (fr) Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif
CN110188096B (zh) 一种数据记录的索引创建方法、装置及设备
WO2020211569A1 (fr) Procédé de construction d'index d'enregistrement de données
WO2020233146A1 (fr) Procédé, système et appareil de stockage d'enregistrement d'opération de données, et dispositif
WO2021017422A1 (fr) Procédé de création d'index dans un livre de comptes de type à chaîne de blocs, dispositif et appareil
TWI706259B (zh) 資料的查詢方法及查詢裝置
TW202008196A (zh) 基於中心化結算與區塊鏈存證的交易方法及系統
WO2020244239A1 (fr) Procédé, appareil et dispositif de création d'indice basés sur un identifiant de service
WO2021073240A1 (fr) Procédé, dispositif et appareil pour stocker des données dans un registre de blockchain
WO2020244238A1 (fr) Procédé, dispositif et appareil de stockage de données utilisant des registres à chaîne de blocs à niveaux multiples
US20120023586A1 (en) Determining privacy risk for database queries
TW202008235A (zh) 基於中心化結算與區塊鏈存證的交易方法及系統
WO2020244237A1 (fr) Procédé, dispositif et appareil de vérification de registre de chaîne de blocs
US10025878B1 (en) Data lineage analysis
CN110162662A (zh) 一种块链式账本中数据记录的验证方法、装置及设备
US10521407B2 (en) Grouping of database objects
WO2020211497A1 (fr) Procédé, système, appareil et dispositif pour stocker un enregistrement de changement de bien personnel
US8533159B2 (en) Processing materialized tables in a multi-tenant application system
WO2021073241A1 (fr) Procédé et dispositif de lecture de données basés sur un stockage sur disque, et appareil
WO2020253231A1 (fr) Procédé et appareil de stockage de données à base de reçu, et dispositif
WO2021093461A1 (fr) Procédé et appareil de calcul d'agrégation dans un registre de chaîne de blocs, et dispositif
US9633081B1 (en) Systems and methods for determining application installation likelihood based on user network characteristics
WO2021057164A1 (fr) Procédé et dispositif d'interrogation pour un registre de chaîne de blocs et appareil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20887252

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20887252

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 05/07/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20887252

Country of ref document: EP

Kind code of ref document: A1