CN114564934B - Software program version difference analysis method, device, equipment and storage medium - Google Patents
Software program version difference analysis method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114564934B CN114564934B CN202210118545.7A CN202210118545A CN114564934B CN 114564934 B CN114564934 B CN 114564934B CN 202210118545 A CN202210118545 A CN 202210118545A CN 114564934 B CN114564934 B CN 114564934B
- Authority
- CN
- China
- Prior art keywords
- version
- software program
- file
- digest
- name
- 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
- 238000004458 analytical method Methods 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000008569 process Effects 0.000 claims abstract description 11
- 238000012795 verification Methods 0.000 claims abstract description 11
- 238000004590 computer program Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 claims description 8
- 239000002699 waste material Substances 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 4
- 239000000835 fiber Substances 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000033764 rhythmic process Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/194—Calculation of difference between files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The application provides a software program version difference analysis method, which specifically comprises the following steps: acquiring each element contained in the release version of the software program, defining each element through a URL to form element content, abstracting the defined element content by adopting a message abstract algorithm, and generating a version abstract of the release version of the software program; further acquiring a summary file of a standard version of the software program; executing a version verification process on the software program needing to be subjected to the difference analysis through a version comparator; and recording the compared differences to form a difference list and storing the difference list. Through definitely defining each element contained in the software program through the URI, simplifying element content by adopting a message digest algorithm, generating a version digest of an operation version, and comparing the version digest with a release digest of a standard version item by item to obtain a difference list, the method can get rid of time and labor waste of manually comparing version differences, and can rapidly analyze the differences of the operation version.
Description
Technical Field
The application belongs to the technical field of software program version difference analysis, and particularly relates to a software program version difference analysis method, device, equipment and storage medium.
Background
Most of the current software programs mainly adopt modes of version numbers, version description files and the like when determining versions. However, in an actual production environment, since the release of the version update usually adopts an incremental release mode, a part of the changed files are updated each time, and in the long-term maintenance process, the production version gradually cannot correspond to the source code version, in particular, a product is applied to a plurality of clients, different clients may have respective release rhythms and requirements, and only a part of the content of the version may be released, so that the later modification needs to be performed for comparing a plurality of versions. And the configuration items of the product (including configuration files and configuration class information in a data table), the table structure of the database, initialization data in the data table and the like can also cause problems in inconsistent with the version requirements. There is therefore a great need for a method to quickly and efficiently analyze version differences and accurately locate specific differences.
In view of this, it is very significant to provide a method, apparatus, device and storage medium for analyzing differences in software program versions.
Content of the application
In order to solve the problem that the existing software program version difference cannot be analyzed rapidly and effectively, the application provides a software program version difference analysis method, device, equipment and storage medium, so as to solve the technical defect problem existing in the prior art.
In a first aspect, the present application proposes a method for analyzing differences between versions of a software program, the method specifically including the following steps:
s1, acquiring each element contained in a release version of a software program, defining each element through a URL to form element content, and abstracting the defined element content by adopting a message abstract algorithm to generate a version abstract of the release version of the software program;
s2, further acquiring a summary file of a standard version of the software program;
s3, executing a version verification process on the software program needing to be subjected to difference analysis through a version comparator; and
s4, recording the compared differences to form a difference list and storing the difference list.
The method comprises the steps of definitely defining each element contained in an operating version of a software program through URI, simplifying element content by adopting a message digest algorithm, generating a version digest of the operating version, and comparing the version digest with a release digest of a standard version item by item to obtain a difference list. The differences between the running version and each version can be analyzed by comparing the running version with the published abstracts of a plurality of standard versions, the nearest version can be found, and the subsequent upgrading can be carried out; the method and the device have the advantages that time and labor are wasted in manual comparison of version differences can be eliminated, the influence of misoperation caused by manual comparison is avoided, the differences of running versions can be rapidly analyzed, and particularly, the difficult-to-compare contents such as configuration items and initialization data can be timely and accurately generated.
Preferably, the version verification process in S3 specifically includes:
s31, the version comparator acquires the URL of each element of the software program version to be analyzed, searches in the abstract file of the software program standard version acquired in S2, and judges and marks that the URL of each element belongs to three states of existing, non-existing or missing;
s32, if the URL of the element belongs to the existing state, abstracting the element content by using the message abstracting algorithm in the abstracting file of the software program standard version, and comparing with the abstracting file of the software program standard version, and judging and marking the two states as the existing state and the existing state.
Preferably, the elements include release files, configuration items, database table structures, and initialization data.
Further preferably, the release file includes a non-configuration file and a configuration file, and the URI format of the non-configuration file is: file:// [ war package name ]/file path/file name, and abstracting the whole content of the release file; the URI format of the configuration file is: filecon fig:// [ war package name ]/file path/file name;
the URI format is: the name of the configuration item is summarized by the configuration item value;
the URI formats of the tables, fields, indexes, stored procedures and custom functions in the database are as follows: [ mysql|oracle|db2|sqlserver| … ]/[ table|field|index|sp| udf ]/name, abstract the whole text of the corresponding database DDL statement;
the URI format of the initialization data is: record:// table name/primary key value, converting all field values of the corresponding record into character strings, and then splicing with 'I' to be used as abstract.
Preferably, the summary file of the standard version includes:
the first line displays the product name, version number, release date, message digest algorithm name, and adjacent lines are separated by commas;
the second row starts with each element row, and the format of each row is as follows: URL = digest value.
Preferably, the difference list includes: each element is in a row, and the format of each row is as follows: URL, status flag, standard version digest value, run version digest value; the status flags include existing consistency, existing inconsistency, absence, and absence.
Preferably, the message digest algorithm includes MD2, MD4 and MD5.
In a second aspect, the present application further proposes an apparatus for software program version difference analysis, including:
the acquisition module is used for: configuring each element and abstract file for acquiring the software program;
the definition module: the method comprises the steps of configuring the acquired elements to be defined through URLs;
version digest generator module: configured to digest the defined elements by a message digest algorithm;
version comparator module: configured for analysis and comparison of differences in versions of the software program;
and a judging module: the method comprises the steps of configuring the device for judging and marking the difference;
and a recording module: configured to record the analyzed differences and form a difference list.
In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; and storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method as described in any of the implementations of the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method as described in any of the implementations of the first aspect.
Compared with the prior art, the beneficial results of the application are as follows:
(1) The method comprises the steps of definitely defining each element contained in an operating version of a software program through URI, simplifying element content by adopting a message digest algorithm, generating a version digest of the operating version, and comparing the version digest with a release digest of a standard version item by item to obtain a difference list.
(2) The differences between the running version and each version can be analyzed by comparing the running version with the published abstracts of a plurality of standard versions, the nearest version can be found, and the subsequent upgrading can be carried out; the method and the device have the advantages that time and labor are wasted in manual comparison of version differences can be eliminated, the influence of misoperation caused by manual comparison is avoided, the differences of running versions can be rapidly analyzed, and particularly, the difficult-to-compare contents such as configuration items and initialization data can be timely and accurately generated.
Drawings
The accompanying drawings are included to provide a further understanding of the embodiments and are incorporated in and constitute a part of this specification. The accompanying drawings illustrate embodiments and, together with the description, serve to explain the principles of the present application. Many of the intended advantages of other embodiments and embodiments will be readily appreciated as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.
FIG. 1 is an exemplary device frame pattern to which an embodiment of the present application may be applied;
FIG. 2 is a flow chart of a software program version difference analysis method according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a software program version difference analysis method according to an embodiment of the present application;
FIG. 4 is a schematic flow chart of S3 in a software program version difference analysis method according to an embodiment of the present application;
FIG. 5 is a flow chart of a software program version difference analysis device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a computer device suitable for use in implementing the embodiments of the present application.
Detailed Description
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the application may be practiced. For this, directional terms, such as "top", "bottom", "left", "right", "upper", "lower", and the like, are used with reference to the orientation of the described figures. Because components of embodiments can be positioned in a number of different orientations, the directional terminology is used for purposes of illustration and is in no way limiting. It is to be understood that other embodiments may be utilized or logical changes may be made without departing from the scope of the present application. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present application is defined by the appended claims.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 1 illustrates an exemplary system architecture 100 to which the methods for processing information or the apparatuses for processing information of the embodiments of the present application may be applied.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be various electronic devices with communication capabilities including, but not limited to, smartphones, tablet computers, laptop and desktop computers, and the like.
The server 105 may be a server that provides various services, such as a background information processing server that processes verification request information transmitted by the terminal devices 101, 102, 103. The background information processing server may analyze the received verification request information and obtain a processing result (for example, verification success information for characterizing that the verification request is a legal request).
It should be noted that, the method for processing information provided in the embodiment of the present application is generally performed by the server 105, and accordingly, the device for processing information is generally disposed in the server 105. In addition, the method for transmitting information provided by the embodiments of the present application is generally performed by the terminal devices 101, 102, 103, and accordingly, the means for transmitting information is generally provided in the terminal devices 101, 102, 103.
The server may be hardware or software. When the server is hardware, the server may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules (e.g., to provide distributed services), or as a single software or a plurality of software modules. The present invention is not particularly limited herein.
In a first aspect, an embodiment of the present application discloses a software program version difference analysis method, referring to fig. 2 and fig. 3, the method specifically includes the following steps:
s1, acquiring each element contained in a release version of a software program, defining each element through a URL to form element content, and abstracting the defined element content by adopting a message abstract algorithm to generate a version abstract of the release version of the software program;
s2, further acquiring a summary file of a standard version of the software program;
s3, executing a version verification process on the software program needing to be subjected to difference analysis through a version comparator;
specifically, referring to fig. 4, in this embodiment, the version verification process in S3 specifically includes: s31, a version comparator acquires URLs of all elements of the software program version to be analyzed, searches in the abstract file of the software program standard version acquired in S2, and judges and marks that the URLs of all the elements belong to three states of existing, non-existing or missing;
s32, if the URL of the element belongs to the existing state, abstracting the element content by using a message abstracting algorithm in an abstracting file of a software program standard version, and comparing the abstracted content with the abstracting file of the software program standard version, and judging and marking the abstracted content as the existing state and the existing inconsistent state.
S4, recording the compared differences to form a difference list and storing the difference list.
In particular, in the embodiment, the message digest algorithm includes MD2, MD4, and MD5, and in this embodiment, the MD5 digest algorithm is used.
In the present embodiment, each element included in the software program includes, but is not limited to, a release file, a configuration item, a database table structure, initialization data, and the like.
The release file comprises a non-configuration file and a configuration file, wherein the URI format of the non-configuration file is as follows: file:// [ war package name ]/file path/file name, which abstracts the content of the released file in its entirety; the URI format of the configuration file is: filecon fig:// [ war package name ]/file path/file name;
the URI format is: the name of the configuration item is summarized by the configuration item value;
the URI formats of the tables, fields, indexes, stored procedures, custom functions in the database are: [ mysql|oracle|db2|sqlserver| … ]/[ table|field|index|sp| udf ]/name, abstract the whole text of the corresponding database DDL statement;
the URI format of the initialization data is: record// table name/primary key value, converting the character strings with all field values corresponding to the records, and then splicing with 'I' to be used as a abstract;
the URI format of the configuration item data is: dbconfig// table name/primary key value, abstracting the key field value of the configuration item.
In addition, the content which is not in the above range and needs to be controlled in version can be subjected to the digest algorithm by defining the URI and checking the content according to the requirement.
Further, the summary file of the standard version includes:
the first line displays the product name, version number, release date, message digest algorithm name, and adjacent lines are separated by commas;
the second row starts one row per element, each row having the format: URL = digest value.
The difference list includes: each element is in a row, and the format of each row is as follows: URL, status flag, standard version digest value, run version digest value; status flags include existing consistency, existing inconsistency, absence, and absence.
According to the scheme, all elements contained in the running version of the software program are definitely defined through URIs, the element content is reduced by adopting a message digest algorithm, a version digest of the running version is generated, and the version digest is compared with a release digest of a standard version item by item to obtain a difference list. The differences between the running version and each version can be analyzed by comparing the running version with the published abstracts of a plurality of standard versions, the nearest version can be found, and the subsequent upgrading can be carried out; the method and the device have the advantages that time and labor are wasted in manual comparison of version differences can be eliminated, the influence of misoperation caused by manual comparison is avoided, the differences of running versions can be rapidly analyzed, and particularly, the difficult-to-compare contents such as configuration items and initialization data can be timely and accurately generated.
In a second aspect, an embodiment of the present application further provides an apparatus for analyzing differences between versions of a software program, referring to fig. 5, including:
the acquisition module 51: configuring each element and abstract file for acquiring the software program;
definition module 52: the configuration is used for defining the acquired elements through URLs;
version digest generator module 53: configured to digest the defined elements by a message digest algorithm;
version comparator module 54: configured for analysis and comparison of differences in versions of the software program;
judgment module 55: the method comprises the steps of configuring the device for judging and marking the difference;
recording module 56: configured to record the analyzed differences and form a difference list.
Referring now to fig. 6, there is illustrated a schematic diagram of a computer apparatus 600 suitable for use in implementing an electronic device (e.g., a server or terminal device as illustrated in fig. 1) of an embodiment of the present application. The electronic device shown in fig. 6 is only an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present application.
As shown in fig. 6, the computer apparatus 600 includes a Central Processing Unit (CPU) 601 and a Graphics Processor (GPU) 602, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 603 or a program loaded from a storage section 609 into a Random Access Memory (RAM) 606. In the RAM 604, various programs and data required for the operation of the apparatus 600 are also stored. The CPU 601, GPU602, ROM 603, and RAM 604 are connected to each other through a bus 605. An input/output (I/O) interface 606 is also connected to the bus 605.
The following components are connected to the I/O interface 606: an input portion 607 including a keyboard, a mouse, and the like; an output portion 608 including a speaker, such as a Liquid Crystal Display (LCD), etc.; a storage portion 609 including a hard disk and the like; and a communication section 610 including a network interface card such as a LAN card, a modem, or the like. The communication section 610 performs communication processing via a network such as the internet. The drive 611 may also be connected to the I/O interface 606 as needed. A removable medium 612 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 611 as necessary, so that a computer program read out therefrom is mounted into the storage section 609 as necessary.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 610, and/or installed from the removable medium 612. The above-described functions defined in the method of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 601 and a Graphics Processor (GPU) 602.
It should be noted that the computer readable medium described in the present application may be a computer readable signal medium or a computer readable medium, or any combination of the two. The computer readable medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor apparatus, device, or means, or a combination of any of the foregoing. More specific examples of the computer-readable medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution apparatus, device, or apparatus. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may be any computer readable medium that is not a computer readable medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution apparatus, device, or apparatus. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based devices which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments described in the present application may be implemented by software, or may be implemented by hardware. The described modules may also be provided in a processor.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the method of software program version difference analysis described above.
The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the invention referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the invention. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.
Claims (9)
1. A software program version difference analysis method is characterized by comprising the following steps:
s1, acquiring each element contained in a release version of a software program, defining each element through a URL to form element content, and abstracting the defined element content by adopting a message abstract algorithm to generate a version abstract of the release version of the software program;
s2, further acquiring a summary file of a standard version of the software program;
s3, executing a version verification process on the software program needing to be subjected to difference analysis through a version comparator; and
s4, recording and storing the compared differences to form a difference list;
the version verification process in S3 specifically includes:
s31, the version comparator acquires the URL of each element of the software program version to be analyzed, searches in the abstract file of the software program standard version acquired in S2, and judges and marks that the URL of each element belongs to three states of existing, non-existing or missing;
s32, if the URL of the element belongs to the existing state, abstracting the element content by using the message abstracting algorithm in the abstracting file of the software program standard version, and comparing with the abstracting file of the software program standard version, and judging and marking the two states as the existing state and the existing state.
2. The software program version difference analysis method according to claim 1, wherein the elements include a release file, a configuration item, a database table structure, and initialization data.
3. The software program version difference analysis method according to claim 2, wherein the release file includes a non-configuration file and a configuration file, and the URI format of the non-configuration file is: file:// [ war package name ]/file path/file name, and abstracting the whole content of the release file; the URI format of the configuration file is: filecon fig:// [ war package name ]/file path/file name;
the URI format is: the name of the configuration item is summarized by the configuration item value;
the URI formats of the tables, fields, indexes, stored procedures and custom functions in the database are as follows: [ mysql|oracle|db2|sqlserver| … ]/[ table|field|index|sp| udf ]/name, abstract the whole text of the corresponding database DDL statement;
the URI format of the initialization data is: record:// table name/primary key value, converting all field values of the corresponding record into character strings, and then splicing with 'I' to be used as abstract.
4. The software program version difference analysis method according to claim 1, wherein the digest file of the standard version comprises:
the first line displays the product name, version number, release date, message digest algorithm name, and adjacent lines are separated by commas;
the second row starts with each element row, and the format of each row is as follows: URL = digest value.
5. The software program version difference analysis method according to claim 1, wherein the difference list includes: each element is in a row, and the format of each row is as follows: URL, status flag, standard version digest value, run version digest value; the status flags include existing consistency, existing inconsistency, absence, and absence.
6. The software program version difference analysis method according to claim 1, wherein the message digest algorithm includes MD2, MD4 and MD5.
7. An apparatus for software program version difference analysis, comprising:
the acquisition module is used for: configuring each element and abstract file for acquiring the software program;
the definition module: the method comprises the steps of configuring the acquired elements to be defined through URLs;
version digest generator module: configured to digest the defined elements by a message digest algorithm;
version comparator module: configured for analysis and comparison of differences in versions of the software program;
and a judging module: the method comprises the steps of configuring the device for judging and marking the difference;
and a recording module: configured to record the analyzed differences and form a difference list.
8. An electronic device, comprising:
one or more processors;
a storage means for storing one or more programs;
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-6.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118545.7A CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118545.7A CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114564934A CN114564934A (en) | 2022-05-31 |
| CN114564934B true CN114564934B (en) | 2024-03-22 |
Family
ID=81713475
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210118545.7A Active CN114564934B (en) | 2022-02-08 | 2022-02-08 | Software program version difference analysis method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564934B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN110457628A (en) * | 2019-07-05 | 2019-11-15 | 平安国际智慧城市科技股份有限公司 | Webpage edition correcting method, device, equipment and storage medium |
| CN113157315A (en) * | 2021-04-30 | 2021-07-23 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for identifying difference information of different versions of software |
| CN113225729A (en) * | 2020-01-21 | 2021-08-06 | 荣耀终端有限公司 | OTA (over the air) upgrading method and device and readable storage medium |
| CN113326058A (en) * | 2021-07-01 | 2021-08-31 | 苏州好玩友网络科技有限公司 | Method, device, equipment and medium for updating version of application |
| CN113778510A (en) * | 2021-08-17 | 2021-12-10 | 珠海西山居移动游戏科技有限公司 | Multi-version maintenance method and device for application program and readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8495612B2 (en) * | 2011-10-21 | 2013-07-23 | International Business Machines Corporation | Systems and methods for upgrading a version of software |
-
2022
- 2022-02-08 CN CN202210118545.7A patent/CN114564934B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN110457628A (en) * | 2019-07-05 | 2019-11-15 | 平安国际智慧城市科技股份有限公司 | Webpage edition correcting method, device, equipment and storage medium |
| CN113225729A (en) * | 2020-01-21 | 2021-08-06 | 荣耀终端有限公司 | OTA (over the air) upgrading method and device and readable storage medium |
| CN113157315A (en) * | 2021-04-30 | 2021-07-23 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for identifying difference information of different versions of software |
| CN113326058A (en) * | 2021-07-01 | 2021-08-31 | 苏州好玩友网络科技有限公司 | Method, device, equipment and medium for updating version of application |
| CN113778510A (en) * | 2021-08-17 | 2021-12-10 | 珠海西山居移动游戏科技有限公司 | Multi-version maintenance method and device for application program and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114564934A (en) | 2022-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10521404B2 (en) | Data transformations with metadata | |
| US11620400B2 (en) | Querying in big data storage formats | |
| US10055444B2 (en) | Systems and methods for access control over changing big data structures | |
| US10459881B2 (en) | Data management platform using metadata repository | |
| US8468391B2 (en) | Utilizing log event ontology to deliver user role specific solutions for problem determination | |
| US10360394B2 (en) | System and method for creating, tracking, and maintaining big data use cases | |
| US10956438B2 (en) | Catalog with location of variables for data | |
| CN109359194B (en) | Method and apparatus for predicting information categories | |
| CN110321544B (en) | Method and device for generating information | |
| US10043138B2 (en) | Metadata representation and storage | |
| GB2499500A (en) | Document merge | |
| CN110795649A (en) | Target page display method, device and system and electronic equipment | |
| CN111125064B (en) | Method and device for generating database schema definition statement | |
| CN109460363B (en) | Automatic testing method and device, electronic equipment and computer readable medium | |
| CN112818026A (en) | Data integration method and device | |
| CN108694172B (en) | Information output method and device | |
| CN113377342B (en) | Project construction method and device, electronic equipment and storage medium | |
| CN114564934B (en) | Software program version difference analysis method, device, equipment and storage medium | |
| CN111858621B (en) | Method, apparatus, device and computer readable medium for monitoring business process | |
| CN116414855A (en) | Information processing method and device, electronic equipment and computer readable storage medium | |
| CN109901934B (en) | Method and device for generating interface help document | |
| US20060048094A1 (en) | Systems and methods for decoupling inputs and outputs in a workflow process | |
| CN110196803B (en) | Software defect training method and system | |
| US20220114189A1 (en) | Extraction of structured information from unstructured documents | |
| CN112965946B (en) | Method, device, equipment and computer readable medium for processing document |
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 |