CN111177302B - Service bill processing method, device, computer equipment and storage medium - Google Patents
Service bill processing method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111177302B CN111177302B CN201911300217.3A CN201911300217A CN111177302B CN 111177302 B CN111177302 B CN 111177302B CN 201911300217 A CN201911300217 A CN 201911300217A CN 111177302 B CN111177302 B CN 111177302B
- Authority
- CN
- China
- Prior art keywords
- version
- target
- service data
- type
- data
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 24
- 238000012508 change request Methods 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 10
- 230000008859 change Effects 0.000 claims description 36
- 238000004590 computer program Methods 0.000 claims description 14
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 238000003780 insertion Methods 0.000 claims description 4
- 230000037431 insertion Effects 0.000 claims description 4
- 238000012384 transportation and delivery Methods 0.000 description 14
- 239000000463 material Substances 0.000 description 12
- 238000010586 diagram Methods 0.000 description 9
- 238000000547 structure data Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 238000013515 script Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—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/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
-
- 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
- G06F16/316—Indexing structures
- G06F16/322—Trees
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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)
- Software Systems (AREA)
- Library & Information Science (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a business document processing method, a business document processing device, computer equipment and a storage medium. The method comprises the following steps: receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service bill, and the initial service data comprises a plurality of fields and field values corresponding to the fields; forming text objects by the fields and the corresponding field values; acquiring the hierarchical relation among fields in the target business document, and combining each text object according to the hierarchical relation among the fields to obtain a combined text object; and obtaining target service data corresponding to the initial service data according to the combined text object. By adopting the method, the data redundancy can be reduced.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a service document processing method, device, computer device, and storage medium.
Background
With the development of computer technology, various types of databases, such as relational databases and non-relational databases, are continuously developed. More and more businesses employ databases to store business documents, such as ERP (Enterprise Resource Planning ) systems that employ physical tables and columns of the databases to store ERP business documents, such as sales orders, purchase orders, and the like.
However, the physical table and the field column of the database are adopted to store data, so that the storage comparison of the data is scattered and complicated, and the data redundancy is high.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a business document processing method, apparatus, computer device, and storage medium capable of reducing data redundancy in order to solve the above-mentioned technical problem of high data redundancy.
A business document processing method, the method comprising: receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service bill, and the initial service data comprises a plurality of fields and field values corresponding to the fields; forming text objects by the fields and the corresponding field values; acquiring the hierarchical relation among fields in the target business document, and combining each text object according to the hierarchical relation among the fields to obtain a combined text object; and obtaining target service data corresponding to the initial service data according to the combined text object.
In some embodiments, the text object is a key value pair, and the composing each of the fields and the corresponding field value into the text object includes: taking each field as a key, and taking the corresponding field value as a value to obtain a key value pair corresponding to each field; the step of obtaining the hierarchical relationship between the fields in the target business document, and combining each text object according to the hierarchical relationship between the fields to obtain a combined text object, including: and acquiring the hierarchical relation among the fields in the target business document, and combining the key value pairs by the hierarchical relation among the fields to obtain a combined text object.
In some embodiments, the method further comprises: acquiring a preset field; taking the target service data as a field value corresponding to the preset field to establish a corresponding relation between the preset field and the target service data; and storing the target service data in the preset field.
In some embodiments, the target service data is a first version service data corresponding to the target service document, and the method further includes: receiving a version comparison request corresponding to the target business bill, wherein the version comparison request carries a first version identifier and a second version identifier; responding to the version comparison request, extracting the combined text object from the target service data, and taking the combined text object as first version service data corresponding to the first version identification; splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree; acquiring a second object tree corresponding to the second version identifier; and comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business document.
In some embodiments, the version comparison request further carries a version type corresponding to a version identifier, and comparing the differences between the first object tree and the second object tree to obtain a version comparison result of the target business document includes: acquiring objects with differences in the first object tree and the second object tree as target objects; acquiring a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier; determining a change operation type corresponding to the target object according to the first version type and the second version type; and taking the target object and the version change operation type as a version comparison result.
In some embodiments, the obtaining the object with the difference in the first object tree and the second object tree includes: acquiring objects only existing in the first object tree or the second object tree as target objects; the determining the change operation type corresponding to the target object according to the first version type and the second version type includes: when the first version type is a reference version type and the second version type is a comparison version type, determining that a change operation type corresponding to a target object only existing in the first object tree is a deletion operation type; and when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
In some embodiments, the obtaining the first version type corresponding to the first version identifier and the second version type corresponding to the second version identifier includes: receiving a reference version selection operation and a comparison version selection operation through a version change comparison interface; and taking the candidate version identifier indicated to be selected by the reference version selection operation as a first version identifier, wherein the first version type corresponding to the first version identifier is the reference version type, and taking the candidate version identifier indicated to be selected by the comparison version selection operation as a second version identifier, and the second version type corresponding to the second version identifier is the comparison version type.
A business document processing apparatus, the apparatus comprising: the system comprises a data format change request receiving module, a data format change request receiving module and a data processing module, wherein the data format change request receiving module is used for receiving a data format change request of initial service data, the initial service data is data corresponding to a target service bill, and the initial service data comprises a plurality of fields and field values corresponding to the fields; the text object composition module is used for composing each field and the corresponding field value into a text object; the combined text object obtaining module is used for obtaining the hierarchical relation between the fields in the target business document, and combining the text objects according to the hierarchical relation between the fields to obtain a combined text object; and the target service data obtaining module is used for obtaining target service data corresponding to the initial service data according to the combined text object.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the business document processing method described above when the computer program is executed by the processor.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the business document processing method described above.
According to the business document processing method, the device, the computer equipment and the storage medium, the data format change request of the initial business data is received, the initial business data is data corresponding to the target business document, the initial business data comprises a plurality of fields and field values corresponding to the fields, the fields and the corresponding field values form text objects, the hierarchical relation among the fields in the target business document is obtained, the text objects are combined according to the hierarchical relation among the fields to obtain combined text objects, and the target business data corresponding to the initial business data is obtained according to the combined text objects, so that the mode of converting the initial business data into the combined text objects is realized for storage, the data is not represented in a physical table and field column form of a complex database, and the redundancy of the data is reduced.
Drawings
FIG. 1 is an application scenario diagram of a business document processing method in some embodiments;
FIG. 2A is a flow chart of a business document processing method in some embodiments;
FIG. 2B is a schematic diagram of a business document in some embodiments;
FIG. 2C is a schematic diagram of a business document processing method in some embodiments;
FIG. 2D is a diagram of a packet according to some embodiments;
FIG. 3 is a flow chart of a business document processing method in some embodiments;
FIG. 4 is a flow chart of a business document processing method in some embodiments;
FIG. 5A is a flowchart illustrating a version comparison result obtaining step in some embodiments;
FIG. 5B is a schematic diagram of a version change comparison interface in some embodiments;
FIG. 5C is a schematic diagram of a packet structure in some embodiments;
FIG. 6 is a flowchart illustrating a version comparison result obtaining step in some embodiments;
FIG. 7 is a flowchart of a version comparison result obtaining step in some embodiments;
FIG. 8 is a flowchart of a version comparison result obtaining step in some embodiments;
FIG. 9 is a block diagram of an architecture of a business document processing device in some embodiments;
FIG. 10 is an internal block diagram of a computer device in some embodiments.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The business document processing method provided by the application can be applied to an application environment shown in fig. 1. The application environment includes a terminal 102 and a server 104. Wherein the terminal 102 communicates with the server 104 via a network. The server 104 is used for managing service documents, and may be a server corresponding to a service document management system, where the service document management system may be, for example, an ERP system, and the service documents may be, for example, a sales order, a purchase order, and the like. The server 104 may provide a web page or a client for accessing the server 104, and a business person of the business document management system may access the web page or the client corresponding to the server 104 through the terminal 102 and may operate on the web page or the client.
Specifically, the service personnel can access the web page or the client corresponding to the server 104 through the terminal 102, create a service document, modify the service document, and the like. The same business document may include multiple altered versions. In general, a business document often needs to be changed in the execution process, and each changed version needs to be kept and stored, and each changed document passing verification is a changed version. In general, the modified version is stored and is not modified any more, and can be used for archiving, historical query and version comparison and peer-to-peer. The server 104 may perform format conversion on the initial service data corresponding to the changed version, obtain service data after format conversion, and store the service data after format conversion. The initial service data may include a plurality of fields and field values corresponding to the respective fields.
When the service personnel performs the operation of storing the changed version on the webpage or the client corresponding to the server 104, the data format change request can be triggered to be sent to the server 104, where the data format change request can carry the data corresponding to the target service bill, that is, the initial service data. The server 104 may receive the data format change request, and form text objects from each field of the initial service data and the corresponding field value according to the data format change request, may obtain a hierarchical relationship between fields in the service document, combine each text object according to the hierarchical relationship between fields, obtain a combined text object, and may obtain the service data after format conversion according to the combined text object. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 104 may be implemented by a stand-alone server or a server cluster composed of a plurality of servers.
In some embodiments, as shown in fig. 2A, a business document processing method is provided, and the method is applied to the server 104 in fig. 1 for illustration, and includes the following steps:
S202, receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service bill, and comprises a plurality of fields and field values corresponding to the fields.
Specifically, the document refers to a carrier for carrying enterprise business data in an enterprise ERP system. For example, sales orders, purchase orders, etc. The target business bill is a business bill which needs to be subjected to data format change. The business document may include a plurality of fields, which may be, for example, document type, document number, business type, document status, delivery style, etc.
In some embodiments, the document may include a document header, a document body, and a sub-document body. The bill header may be one or more, and as shown in fig. 2B, sales orders are shown, wherein the bill header has 2 bill headers, which are basic information and financial information, respectively. The bill header may correspond to a plurality of fields, and the basic information in fig. 2B may include fields such as a bill type, a bill number, a date, a service type, a sales organization, and a delivery mode. The document body may include a plurality of fields, for example, the document body in fig. 2B may include fields such as a serial number, a material code, and a material name, and the document body may further include a plurality of entries, for example, as shown in fig. 2B, a total of 3 entries are displayed, which are an entry corresponding to a serial number 1, an entry corresponding to a serial number 2, and an entry corresponding to a serial number 3. The sub-bill body can be a bill body corresponding to the entry. As shown in fig. 2B, the sub-document body corresponds to entry with sequence number 2. One entry may correspond to multiple sub-document bodies.
In some embodiments, the initial service data may be a service data packet corresponding to the target service document, and the service data packet may be, for example, a DynamicObject and metadata structure data packet. Wherein DynamicObject represents a dynamic object data packet, wherein an object refers to a business document, and related data of the business document, such as fields and field values in the business document, are included. Because the structure, the number of fields and the field properties of different business documents can be different, the data packet for storing the business documents is called a dynamic object data packet. The business data packet can be bound with the control of the bill interface, so that the bill interface can display the data in the business data packet on the control corresponding to the interface. When the document is updated on the document interface, for example, the operations of modification, storage, submission, verification and the like are performed, the business data packet corresponding to the document can be updated in the same way. The data packet includes a data structure hierarchy and a key value for the data set. The metadata structure refers to the physical structure information of all fields in the business document, including the relationship and hierarchical structure between the fields, such as the document header, document body, sub-document body and other hierarchical relationships.
In some embodiments, when a service person accesses a page corresponding to the server through the terminal, modifies the service document and clicks a generate change version button on the page, a data format change request may be triggered.
S204, forming each field and the corresponding field value into a text object.
In particular, a text object may include one field and one field value. For example, if the initial service data includes a field a and a field B, the field value corresponding to the field a is a, and the field value corresponding to the field B is B, the field a and the field value a may be combined to obtain a text object, which may be represented as { a: a }. The field B and the field value B may be combined to obtain a text object, which may be expressed, for example, as { B: b }.
S206, obtaining the hierarchical relation among the fields in the target business document, and combining each text object according to the hierarchical relation among the fields to obtain a combined text object.
Specifically, the combined text object is a combination of a plurality of text objects. The hierarchical relationship between fields refers to membership between fields. For example, for the basic information in fig. 2B, the fields affiliated with the basic information include the document type, document number, sales organization, and the like. The relationship between fields may be described by a parent-child relationship, for example, the basic information may be parent information, and the document type, document number, and sales organization may be child information of the basic information, respectively.
In some embodiments, the hierarchical relationship between fields defines for each field an identification of the corresponding upper level field. Taking fig. 2B as an example, if the identification of the basic information is key1, the identification of the previous field corresponding to the document type may be defined as key1.
In some embodiments, the hierarchical relationship between the fields may further define an identifier of an entry corresponding to the upper level for the sub document body, where the entry may refer to a row of records in the table. Taking fig. 2B as an example, if the entry with the sequence number of 2 corresponds to the key2, the identifier of the previous field corresponding to the sub-document body may be defined as the key2.
In some embodiments, text objects corresponding to fields belonging to a hierarchy may be combined to obtain a combined text object. Taking the record with the number 1 in fig. 2B as an example, the text object that can be obtained includes { number: 1}, { material encoding: XXX-001-000}, { material name: pencil }, { specification model: a }, { sales number: 12}, { pricing units: element, since the 6 text objects belong to the same hierarchy, i.e. all belong to records with sequence number 1, the 6 text objects can be combined together to form a combined text object, which can be expressed, for example, as { sequence number: 1, material coding: XXX-001-000, material name: pencil, specification model: a, sales quantity: 12, pricing units: element }.
In some embodiments, two different combined text objects may be combined to obtain a new combined text object. Taking the sub document body in fig. 2B as an example, the text object corresponding to the entry with the sequence number 1 is { sequence number: 1, delivery quantity: 4, sales factory: f1, delivery person: zhang Sanj, the entry with sequence number 2 corresponds to the text object { sequence number: 2, delivery quantity: 4, sales factory: f2, delivery person: li IV, the text object corresponding to entry with sequence number 3 is { sequence number: 3, delivery quantity: 5, sales factory: f3, delivery person: the combined text object corresponding to the sub document body can be expressed as { { { serial number }: 1, delivery quantity: 4, sales factory: f1, delivery person: zhang Sanj } { sequence number: 2, delivery quantity: 4, sales factory: f2, delivery person: li IV, { sequence number: 3, delivery quantity: 5, sales factory: f3, delivery person: royal }).
And S208, obtaining target service data corresponding to the initial service data according to the combined text object.
Specifically, the combined text object may be combined to obtain a new combined text object, and when the obtained combined text object includes all fields corresponding to the initial service data, the combined text object may be used as the target service data. The target business data may be stored locally or in other database servers.
In some embodiments, the combined text object may be used as the target business data corresponding to the initial business data. For example, text objects corresponding to all fields may be combined according to a hierarchical relationship between the fields to obtain a combined text object, and at this time, the combined text object may be used as target service data corresponding to the initial service data.
In some embodiments, the combined text object may be Json text. The Json text has key-value pairs with hierarchical relationships. For example, the Json text { a: { b: { c:1}, wherein if the key-value pair { c:1} is used as the third layer, the key-value pair { b: { c:1} is used as the second layer, and the key-value pair { a: { b: { c:1} is used as the first layer. As shown in fig. 2C, the original data packet, the DynamicObject, the service data packet and the metadata structure data packet in the figure refer to the same data packet, that is, all data packets corresponding to the target service document, that is, the initial service data. The initial traffic data is serialized into a Json text in fig. 2C. The document interface displays the corresponding background data as metadata structure data packets, when the metadata structure data packets pass the auditing, the metadata structure data packets can be serialized into Json texts for storage, and the serialized Json texts can be stored in one physical field without separately storing numerous fields one by one, so that the storage efficiency is improved, and the data redundancy is reduced. In addition, as shown in fig. 2C, when a certain version of data is displayed, the Json text can be inversely sequenced into a data packet, and the data packet can be displayed by using the data packet as background data binding of a front-end interface, so that the display is convenient and quick.
In the business document processing method, the data format change request of the initial business data is received, the initial business data is data corresponding to the target business document, the initial business data comprises a plurality of fields and field values corresponding to the fields, the fields and the corresponding field values form text objects, the hierarchical relation among the fields in the target business document is obtained, the text objects are combined according to the hierarchical relation among the fields to obtain combined text objects, and the target business data corresponding to the initial business data is obtained according to the combined text objects, so that the mode of converting the initial business data into the combined text objects is realized and stored, the data is not required to be represented in the form of physical tables and field columns of a complex database, and the redundancy of the data is reduced.
In general, ERP service documents have many fields (for example, hundreds of fields) as physical carriers for storing service data information, and when storing service documents, a physical table is generally required to be built in a database to store the service documents. The physical table comprises a plurality of fields, and one field is used as a column of the physical table and is used for storing field values corresponding to the fields. However, using physical tables and fields of a database to store business documents is relatively bulky, scattered and cumbersome, each field is relatively isolated, and the structure and relationship between documents cannot be clearly embodied. When a service document stored in a database needs to be acquired, for example, a historical service document is queried or service documents of different versions are compared, as shown in fig. 2D, a database query script is needed to query and summarize data of all physical columns, however, the database query script usually involves more fields, which results in lengthy scripts, thus the query efficiency is low, and the performance is poor. Therefore, it is inefficient to use physical tables to store and retrieve data related to business documents. By adopting the scheme of the embodiment of the application, a physical table in a huge database is not needed for storing the business document, so that the data redundancy can be reduced, and the storage and acquisition efficiency of the business document can be improved.
In some embodiments, as shown in fig. 3, the text object is a key value pair, and step S204 is to compose each field and the corresponding field value into the text object, including:
s302, each field is used as a key, and the corresponding field value is used as a value, so that a key value pair corresponding to each field is obtained.
Specifically, the key-value pair includes a key (key) and a value (value), where the key serves as an index of the value. Key-value pairs may employ { key: value }, representation form. As shown in fig. 2B, for the field document number and the corresponding field value XXX001, the document number may be used as a key, XXX001 may be used as a value, and a key value pair { document number: XXX001}.
Step S206, obtaining the hierarchical relation among the fields in the target business document, combining each text object according to the hierarchical relation among the fields to obtain a combined text object, comprising:
s304, acquiring the hierarchical relation among the fields in the target business document, and combining each key value pair by the hierarchical relation among the fields to obtain a combined text object.
Specifically, the respective key-value pairs may be combined according to a hierarchical relationship between keys of the respective key-value pairs. For example for key value pair { document type: standard sales order }, { document number: XXX001}, since the upper level of the bill type and the bill number are basic information, namely the bill type and the bill number are fields of the same level, the { bill type: standard sales order }, { document number: XXX001} are combined.
The embodiment of the application combines the fields and the corresponding field values in the form of key value pairs, and has simple combination mode and high efficiency.
In some embodiments, as shown in fig. 4, the method further comprises:
s402, acquiring a preset field.
S404, taking the target service data as a field value corresponding to the preset field to establish a corresponding relation between the preset field and the target service data.
S406, storing the target business data in a preset field.
Specifically, the preset field may be preset according to a specific service scenario. The preset field can be used as a field of the target service data in the database, and the target service data is inserted into the database, so that the target service data is stored in one physical field, namely, the initial service data is stored in one physical field.
According to the embodiment of the application, the corresponding relation between the preset field and the target service data is established, so that the preset field can be used as the field of the target service data in the database, and the target service data is inserted into the database, thereby realizing that the data corresponding to the target service bill is stored as a whole, improving the storage efficiency and reducing the data redundancy.
In some embodiments, the target service data is a first version of service data corresponding to the target service document, as shown in fig. 5A, and the method further includes:
s502, receiving a version comparison request corresponding to a target business bill, wherein the version comparison request carries a first version identifier and a second version identifier.
Specifically, the target business document may correspond to multiple versions. The version comparison request is used for requesting comparison of different versions of data of the target business document. The version identification is used to uniquely identify a specific version of the target business document. The version identification may include a version number and a document encoding. Different versions of the target business bill have the same bill code and different version numbers. As shown in the document version area in fig. 5B, 3 versions of a document encoded as XXX-001 are shown, with version numbers 000, 001 and 003, respectively. Version identifications are "000 and XXX-001", "001 and XXX-001", and "002 and XXX-001", respectively. Document codes of target business documents corresponding to different business documents are different. For example, the receipt code corresponding to the sales order may be denoted as XXX-002, the receipt code corresponding to the purchase order may be denoted as XXX-012, and the receipt codes of the sales order and the purchase order may not be identical.
In some embodiments, the server may correspond to a version change comparison interface, and the service personnel may select any version on the version change comparison interface corresponding to the target service document to perform comparison, and trigger to send a version comparison request corresponding to the target service document to the server. As shown in fig. 5B, a version change comparison interface corresponding to a document with a document code of XXX-001 is shown, a reference version may be selected in a document version area on the version change comparison interface, then a view button corresponding to a non-reference version is clicked, for example, a document with a version number of 000 is selected as a reference version, a view button corresponding to a document with a version number of 001 is clicked, so that a first version identifier may be "000 and XXX-001", a second version identifier may be "001 and XXX-001", and a comparison between a document with a document code of XXX-001 and a document with a version number of 000 and a document with a version number of xx-001 is shown.
S504, responding to the version comparison request, extracting a combined text object from the target service data, and taking the combined text object as first version service data corresponding to the first version identification.
Specifically, the server may obtain the version identifier in the version comparison request, find the corresponding target service data according to the version identifier, and obtain the combined object corresponding to the target service data as the version service data corresponding to the version identifier.
S506, splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree.
Specifically, a tree is a data structure, and an object tree refers to a structure between objects that presents a tree structure. A combined text object may be split into multiple objects. For example, for a combined text object { sequence number: 1, material coding: XXX-001-000, material name: pencil }, including 3 fields and corresponding field value, because the level that these 3 fields of serial number, material code and material name are located is the same, consequently the level of corresponding 3 objects is also the same, consequently, can split the combination text object into 3 objects, are { serial number: 1} { material encoding: XXX-001-000 { material names: pencil }.
In some embodiments, the combined text object is a Json text, the Json text may be split into a plurality of key-value pairs according to a hierarchical relationship between key-value pairs in the Json text, and one key-value pair may be an object. As shown in fig. 2C, the Json text may be deserialized to obtain a business data packet having an object tree structure.
S508, a second object tree corresponding to the second version identification is obtained.
In some embodiments, the object tree structure is a structure of a service data packet corresponding to a service document, and as shown in fig. 5C, the structure of two service data packets of different versions is shown, where Head represents a document header, subHead represents a sub-document header, row1 represents an entry, and SubRow1 represents a sub-entry or sub-document body to which entry Row1 belongs. Row2 represents another entry. The Head may be represented as the root of the object tree, subHead, row1, and Row2 as the next level objects of the root, and SubRow1 as the next level objects of Row 1.
S510, comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business document.
Specifically, the objects in the positions corresponding to the first object tree and the second object tree can be compared to obtain the difference between the first object tree and the second object tree, and the difference is used as a version comparison result of the target business document.
In some embodiments, the objects in the object tree are key-value pairs, and whether the keys and the values of the key-value pairs in the same position are the same may be compared to obtain the difference between the first object tree and the second object tree. For example, key value pairs at the same position of the first object tree and the second object tree are { sales number, 20} and { sales number, 24} respectively, and the values of the two key value pairs are different.
In the embodiment of the application, when different versions of the target business document need to be compared, the corresponding object tree can be obtained directly according to the target business data for comparison, and the object tree does not need to be obtained according to a large number of isolated fields, so that the comparison efficiency of the business document data of different versions is improved. In addition, by serializing the service data packet into the json form, the structural integrity and consistency of the historical version data are ensured, and the historical version can be conveniently, rapidly and efficiently stored, displayed and compared.
In some embodiments, the version comparison request further carries a version type corresponding to the version identifier, as shown in fig. 6, step S510 is comparing differences between the first object tree and the second object tree, and obtaining a version comparison result of the target business document includes:
s602, obtaining objects with differences in the first object tree and the second object tree as target objects.
Specifically, the object with the difference may be an object that exists in the first object tree and an object that does not exist in the second object tree, or an object that exists in the second object tree and does not exist in the first object tree, or an object that exists in the first object tree and the second object tree and has different corresponding fields or field values.
S604, a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier are obtained.
S606, determining the change operation type corresponding to the target object according to the first version type and the second version type.
In particular, the version types may include a reference version type and a comparison version type. The change operation type may include addition, deletion, modification, and the like. When the first version type is the reference version type and the second version type is the comparison version type, if the target object is an object existing in the first object tree and an object not existing in the second object tree, determining that the change type corresponding to the target object is a deletion operation, if the target object is an object existing in the second object tree and an object not existing in the first object tree, determining that the change type corresponding to the target object is an addition operation, and if the target object is an object existing in the first object tree and the second object tree and corresponding fields or field values are different, determining that the change operation type corresponding to the target object can be a modification operation, for example, modifying a field or modifying a field value.
S608, the target object and the version change operation type are used as a version comparison result.
Specifically, the version comparison result may be the content of the newly added target object, the deleted target object, or the modified target object.
In the embodiment of the application, the version comparison result of the target business document is obtained by comparing the objects at the same position in different object trees, so that the comparison mode is simple and the efficiency is high.
In some embodiments, as shown in fig. 7, step S602 obtains, as target objects, objects having differences in the first object tree and the second object tree, including:
s702, acquiring objects only existing in the first object tree or the second object tree as target objects.
Step S606, namely determining the change operation type corresponding to the target object according to the first version type and the second version type includes:
s704, when the first version type is the reference version type and the second version type is the comparison version type, determining that the change operation type corresponding to the target object only existing in the first object tree is the deletion operation type.
S706, when the first version type is the reference version type and the second version type is the comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is the insertion operation type.
In some embodiments, as shown in fig. 8, step S604 of acquiring the first version type corresponding to the first version identifier and the second version type corresponding to the second version identifier includes:
s802, receiving a reference version selection operation and a comparison version selection operation through a version change comparison interface.
Specifically, the reference version selection operation is used for selecting a reference version, and the comparison version selection operation is used for selecting a comparison version. When the reference version and the comparison version are selected, the comparison version is represented as different relative to the reference version.
S804, the candidate version identifier indicated by the reference version selection operation is used as a first version identifier, the first version type corresponding to the first version identifier is the reference version type, the candidate version identifier indicated by the comparison version selection operation is used as a second version identifier, and the second version type corresponding to the second version identifier is the comparison version type.
Specifically, the candidate version identifiers refer to identifiers corresponding to different versions of target service data corresponding to the target service document, and the server may use the candidate version identifier indicated to be selected by the reference version selection operation as a first version identifier and use the candidate version identifier indicated to be selected by the comparison version selection operation as a second version identifier. The version types may include a reference version type and a comparison version type, the version type corresponding to the reference version identifier is the reference version type, and the version type corresponding to the comparison version identifier is the comparison version type.
It should be understood that, although the steps in the flowcharts of the above embodiments are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts of the above embodiments may include a plurality of sub-steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with at least some of the other steps or sub-steps of other steps.
In some embodiments, as shown in fig. 9, there is provided a business document processing apparatus, including: a data format change request receiving module 902, a text object composing module 904, a combined text object obtaining module 906, and a target business data obtaining module 908, wherein:
the data format change request receiving module 902 is configured to receive a data format change request of initial service data, where the initial service data is data corresponding to a target service document, and the initial service data includes a plurality of fields and field values corresponding to the fields.
A text object composition module 904, configured to compose each field and the corresponding field value into a text object.
And the combined text object obtaining module 906 is configured to obtain a hierarchical relationship between fields in the target business document, and combine each text object according to the hierarchical relationship between the fields to obtain a combined text object.
The target service data obtaining module 908 is configured to obtain target service data corresponding to the initial service data according to the combined text object.
In some embodiments, the text object is a key value pair, and the text object composition module 904 is further configured to use each field as a key, and use a corresponding field value as a value, to obtain a key value pair corresponding to each field; the combined text object obtaining module 906 is further configured to obtain a hierarchical relationship between fields in the target business document, where the hierarchical relationship between fields combines the key value pairs to obtain a combined text object.
In some embodiments, the apparatus further comprises:
the preset field acquisition module is used for acquiring the preset field.
And the corresponding relation establishing module is used for taking the target service data as a field value corresponding to the preset field so as to establish the corresponding relation between the preset field and the target service data.
And the storage module is used for storing the target business data in a preset field.
In some embodiments, the target service data is a first version service data corresponding to the target service document, and the apparatus further includes:
the version comparison request receiving module is used for receiving a version comparison request corresponding to the target business document, wherein the version comparison request carries a first version identifier and a second version identifier.
The first version service data obtaining module is used for responding to the version comparison request, extracting and obtaining a combined text object from the target service data, and taking the combined text object as first version service data corresponding to the first version identification.
And the first object tree obtaining module is used for splitting the combined text object into a plurality of objects according to the hierarchical relation among the objects in the combined text object to obtain the first object tree.
The second object tree acquisition module is used for acquiring a second object tree corresponding to the second version identifier;
and the version comparison result obtaining module is used for comparing the difference between the first object tree and the second object tree to obtain the version comparison result of the target business document.
In some embodiments, the version comparison request further carries a version type corresponding to the version identifier, and the version comparison result obtaining module includes:
And the target object acquisition unit is used for acquiring the object with the difference in the first object tree and the second object tree as a target object.
The version type acquisition unit is used for acquiring a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier.
And the change operation type determining unit is used for determining the change operation type corresponding to the target object according to the first version type and the second version type.
And the version comparison result obtaining unit is used for taking the target object and the version change operation type as version comparison results.
In some embodiments, the target object obtaining unit is further configured to obtain, as the target object, an object that exists only in the first object tree or the second object tree;
the change operation type determining unit is further configured to determine that a change operation type corresponding to a target object only existing in the first object tree is a deletion operation type when the first version type is a reference version type and the second version type is a comparison version type; when the first version type is the reference version type and the second version type is the comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is the insertion operation type.
In some embodiments, the version type obtaining unit is further configured to receive a reference version selection operation and a comparison version selection operation through the version change comparison interface; and taking the candidate version identifier indicated to be selected by the reference version selection operation as a first version identifier, wherein the first version type corresponding to the first version identifier is the reference version type, taking the candidate version identifier indicated to be selected by the comparison version selection operation as a second version identifier, and the second version type corresponding to the second version identifier is the comparison version type.
The specific limitation of the service document processing device can be referred to the limitation of the service document processing method hereinabove, and will not be described herein. The modules in the service bill processing device can be realized in whole or in part by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In some embodiments, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements a business document processing method.
It will be appreciated by those skilled in the art that the structure shown in fig. 10 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In some embodiments, a computer device is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the business document processing method described above when executing the computer program.
In some embodiments, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor, implements the steps of the business document processing method described above.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (10)
1. A business document processing method, the method comprising:
receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service bill, and the initial service data comprises a plurality of fields and field values corresponding to the fields;
taking each field as a key, and taking the corresponding field value as a value to obtain a key value pair corresponding to each field;
Acquiring a hierarchical relation among fields in the target business document, and combining each key value pair according to the hierarchical relation among the fields to obtain a combined text object;
obtaining target service data corresponding to the initial service data according to the combined text object;
taking the target service data as a field value corresponding to a preset field;
taking the preset field as a field of the target business data in a database;
and storing the target business data into a database in the preset field.
2. The method of claim 1, wherein the hierarchical relationship between the fields includes an identification of a higher level field to which each field corresponds.
3. The method of claim 1, wherein the target service data is a first version of service data corresponding to the target service document, the method further comprising:
receiving a version comparison request corresponding to the target business bill, wherein the version comparison request carries a first version identifier and a second version identifier;
responding to the version comparison request, extracting the combined text object from the target service data, and taking the combined text object as first version service data corresponding to the first version identification;
Splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree;
acquiring a second object tree corresponding to the second version identifier;
and comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business document.
4. The method of claim 3, wherein the version comparison request further carries a version type corresponding to a version identifier, and the comparing the differences between the first object tree and the second object tree to obtain the version comparison result of the target business document includes:
acquiring objects with differences in the first object tree and the second object tree as target objects;
acquiring a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier;
determining a change operation type corresponding to the target object according to the first version type and the second version type;
and taking the target object and the version change operation type as a version comparison result.
5. The method of claim 4, wherein the obtaining the object having the difference in the first object tree and the second object tree as the target object comprises:
Acquiring objects only existing in the first object tree or the second object tree as target objects;
the determining the change operation type corresponding to the target object according to the first version type and the second version type includes:
when the first version type is a reference version type and the second version type is a comparison version type, determining that a change operation type corresponding to a target object only existing in the first object tree is a deletion operation type;
and when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
6. The method of claim 4, wherein the obtaining the first version type corresponding to the first version identification and the second version type corresponding to the second version identification comprises:
receiving a reference version selection operation and a comparison version selection operation through a version change comparison interface;
and taking the candidate version identifier indicated to be selected by the reference version selection operation as a first version identifier, wherein the first version type corresponding to the first version identifier is the reference version type, and taking the candidate version identifier indicated to be selected by the comparison version selection operation as a second version identifier, and the second version type corresponding to the second version identifier is the comparison version type.
7. A business document processing device, the device comprising:
the system comprises a data format change request receiving module, a data format change request receiving module and a data processing module, wherein the data format change request receiving module is used for receiving a data format change request of initial service data, the initial service data is data corresponding to a target service bill, and the initial service data comprises a plurality of fields and field values corresponding to the fields;
the text object composition module is used for taking each field as a key and taking a corresponding field value as a value to obtain a key value pair corresponding to each field;
the combined text object obtaining module is used for obtaining the hierarchical relation between the fields in the target business document, and combining the key value pairs according to the hierarchical relation between the fields to obtain a combined text object;
the target service data obtaining module is used for obtaining target service data corresponding to the initial service data according to the combined text object;
the device is also for:
taking the target service data as a field value corresponding to a preset field;
taking the preset field as a field of the target business data in a database;
and storing the target business data into a database in the preset field.
8. The apparatus of claim 7, wherein the hierarchical relationship between the fields comprises an identification of a higher level field to which each field corresponds.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the business document processing method of any one of claims 1 to 6 when the computer program is executed by the processor.
10. A computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the business document processing method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911300217.3A CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911300217.3A CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111177302A CN111177302A (en) | 2020-05-19 |
| CN111177302B true CN111177302B (en) | 2024-02-13 |
Family
ID=70624186
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911300217.3A Active CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111177302B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111967387B (en) * | 2020-08-17 | 2023-05-26 | 北京市商汤科技开发有限公司 | Form recognition method, form recognition device, form recognition equipment and computer-readable storage medium |
| CN112434555B (en) * | 2020-10-16 | 2024-04-09 | 泰康保险集团股份有限公司 | Key value pair region identification method and device, storage medium and electronic equipment |
| CN112465612B (en) * | 2020-11-19 | 2024-09-06 | 金蝶软件（中国）有限公司 | Document information processing method, device, computer equipment and storage medium |
| CN112766875A (en) * | 2020-12-29 | 2021-05-07 | 金蝶软件（中国）有限公司 | Receipt data processing method and device, computer equipment and storage medium |
| CN112967121A (en) * | 2021-02-04 | 2021-06-15 | 金蝶软件（中国）有限公司 | Image retrieval method and device and computer storage medium |
| CN112835904A (en) * | 2021-02-04 | 2021-05-25 | 北京电解智科技有限公司 | Data processing method and data processing device |
| CN113656400B (en) * | 2021-07-08 | 2024-02-27 | 上海二三四五网络科技有限公司 | Characteristic data encoding method and device |
| CN113705183B (en) * | 2021-07-16 | 2024-09-20 | 厦门海迈科技股份有限公司 | Web service-oriented electronic form data generation and maintenance method and related equipment |
| CN113535727B (en) * | 2021-07-19 | 2024-04-09 | 北京数码大方科技股份有限公司 | Data output method and device of information system and electronic equipment |
| CN114416235B (en) * | 2021-12-28 | 2024-09-13 | 云镝智慧科技有限公司 | Document display method, device, computer equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965735A (en) * | 2015-06-18 | 2015-10-07 | 北京京东尚科信息技术有限公司 | Apparatus for generating upgrade SQL script |
| CN105912723A (en) * | 2016-05-09 | 2016-08-31 | 统通信（苏州）有限公司 | Storage method of custom field |
| CN108388438A (en) * | 2018-02-07 | 2018-08-10 | 平安普惠企业管理有限公司 | System base table update method, device, computer equipment and storage medium |
| CN108829727A (en) * | 2018-05-09 | 2018-11-16 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN109800388A (en) * | 2017-11-17 | 2019-05-24 | 车伯乐（北京）信息科技有限公司 | A kind of edit methods of JSON data, apparatus and system |
| CN110147413A (en) * | 2019-04-26 | 2019-08-20 | 平安科技（深圳）有限公司 | Date storage method, data query method, apparatus, equipment and storage medium |
| CN110292775A (en) * | 2019-07-01 | 2019-10-01 | 网易（杭州）网络有限公司 | Obtain the method and device of variance data |
| CN110399367A (en) * | 2018-04-12 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Business data processing method, device, computer equipment and storage medium |
-
2019
- 2019-12-16 CN CN201911300217.3A patent/CN111177302B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965735A (en) * | 2015-06-18 | 2015-10-07 | 北京京东尚科信息技术有限公司 | Apparatus for generating upgrade SQL script |
| CN105912723A (en) * | 2016-05-09 | 2016-08-31 | 统通信（苏州）有限公司 | Storage method of custom field |
| CN109800388A (en) * | 2017-11-17 | 2019-05-24 | 车伯乐（北京）信息科技有限公司 | A kind of edit methods of JSON data, apparatus and system |
| CN108388438A (en) * | 2018-02-07 | 2018-08-10 | 平安普惠企业管理有限公司 | System base table update method, device, computer equipment and storage medium |
| CN110399367A (en) * | 2018-04-12 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN108829727A (en) * | 2018-05-09 | 2018-11-16 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN110147413A (en) * | 2019-04-26 | 2019-08-20 | 平安科技（深圳）有限公司 | Date storage method, data query method, apparatus, equipment and storage medium |
| CN110292775A (en) * | 2019-07-01 | 2019-10-01 | 网易（杭州）网络有限公司 | Obtain the method and device of variance data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111177302A (en) | 2020-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111177302B (en) | Service bill processing method, device, computer equipment and storage medium | |
| CN110069449B (en) | File processing method, device, computer equipment and storage medium | |
| CN109558404B (en) | Data storage method, device, computer equipment and storage medium | |
| CN109408746B (en) | Image information query method, image information query device, computer equipment and storage medium | |
| CN108897874B (en) | Method and apparatus for processing data | |
| US11868328B2 (en) | Multi-record index structure for key-value stores | |
| CN115544183A (en) | Data visualization method and device, computer equipment and storage medium | |
| CN112416934A (en) | hive table incremental data synchronization method and device, computer equipment and storage medium | |
| CN115470156A (en) | RDMA-based memory use method, system, electronic device and storage medium | |
| CN117743299A (en) | Database migration method, device, equipment, medium and product | |
| CN115168499B (en) | Database table fragmentation method and device, computer equipment and storage medium | |
| CN110362590A (en) | Data managing method, device, system, electronic equipment and computer-readable medium | |
| CN115858471A (en) | Service data change recording method, device, computer equipment and medium | |
| CN115495452A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN105549912A (en) | Storage method of server cluster simultaneously containing multiple types of operating systems | |
| CN114860806A (en) | Data query method and device of block chain, computer equipment and storage medium | |
| CN112860755B (en) | Service identifier generation method, device, computer equipment and medium | |
| CN112835886A (en) | Data table field adding method and device | |
| CN115905120B (en) | Archive file management method, archive file management device, archive file management computer device and archive file management storage medium | |
| Abawajy et al. | A framework for scalable distributed provenance storage system | |
| CN115168409B (en) | Data query method and device for database sub-tables and computer equipment | |
| CN116880869A (en) | System interface updating method, device, computer equipment and storage medium | |
| CN117076476A (en) | Object information processing method, device, computer equipment and storage medium | |
| CN116126834A (en) | Database migration method, device, computer equipment and storage medium | |
| CN116881290A (en) | Data processing method, apparatus, device, storage medium, and program product |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TG01 | Patent term adjustment |