CN115576597A

CN115576597A - Version control method and system based on version number associated dynamic configuration

Info

Publication number: CN115576597A
Application number: CN202211180786.0A
Authority: CN
Inventors: 刘一蔚; 刘健; 张同虎
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2022-09-27
Filing date: 2022-09-27
Publication date: 2023-01-06

Abstract

The invention relates to a version control method and a system based on version number association dynamic configuration, which realize dynamic version number linkage control by adding a first version identifier and a second version identifier to an update record for respectively judging the version change relationship between the update record and the existing related record, realize multi-version storage of service data based on a relational database, realize multi-version recording by adding an integer type field as a version number and changing the value of the version number of the service data when the service data is newly added or updated each time, avoid the huge cost brought by packaging a version control system, and are far lower than a set of powerful version control system in both learning cost and development and maintenance cost.

Description

Version control method and system based on version number associated dynamic configuration

Technical Field

The invention relates to the technical field of application service and data processing, in particular to a version control method and system based on version number association dynamic configuration.

Background

In the data using process, data content is usually changed in real time according to requirements, so that a plurality of data contents of different versions belonging to the same data item are formed, and therefore, different versions of data contents need to be managed in a targeted manner by using corresponding solutions. A version control system is a system for recording changes in the content of one or several files so that future reference to a particular version revision can be specified on demand. The version control system can backtrack the selected files to the previous state, and can also be used for comparing the change details of the files, recovering the specific change factors of the difference between the data contents of different versions, changing operators and the like.

Various version control systems exist in the prior art, such as Git, SVN, CVS, etc., with Git being the most popular. Git is an open source distributed version control system, developed based on Linux kernel. Because Git adopts a distributed version library mode, server-side software support is not needed, and compared with other version control systems, git has the characteristics of distribution, offline and rapidness.

However, when the existing version control system is applied to a reagent, various problems often exist due to the difference of specific application scenes. Especially for distributed version library control systems similar to Git, because the internal processing logic and working mechanism of the distributed version library control systems do not accord with the conventional thinking, the learning cost of the version control system is extremely high, and the learning period is long; on the other hand, because of the adherence to the open source design, git does not make any authority limit for browsing and modifying the version library, the code confidentiality is poor, and there is a security risk of using the complete clone library to disclose all data contents.

In fact, for conventional simple requirements in business, such as recording historical version values of business data, no additional powerful functions or optimization support need to be provided to meet the required usage requirements, so there is no necessity to have to use a multi-functional version control system. At present, a plurality of Web applications use a relational database to store own service data, and from the practical requirements and the practical application of operation and maintenance management, a solution different from the existing version control system is required to provide a necessary version control function, so that the learning cost and the development and maintenance cost of version control management are reduced for multi-version storage of service data under the relational database.

Disclosure of Invention

In order to solve the defects of the prior art, the invention provides a version control method and a version control system based on version number association dynamic configuration, which realize multi-version storage of service data based on a relational database, realize multi-version recording by increasing an integer type field as a version number and changing the value of the version number when the service data is newly increased or updated each time, avoid the huge cost brought by encapsulating a version control system, and are far lower than the encapsulating of a set of powerful version control system in both learning cost and development and maintenance cost.

In order to achieve the above purpose, the technical scheme adopted by the invention comprises the following steps:

a version control method based on version number association dynamic configuration is characterized by comprising the following steps:

s1, acquiring an update record, and adding a first version identifier and a second version identifier to the update record; the first version identification comprises fixed updating date and updating information of the corresponding updating record; the second version identification comprises a version number preset as a default value;

s2, searching the database according to the name of the updated record, judging whether the related record stored in the database exists or not, and directly storing the updated record into the database when judging that the related record stored in the database does not exist;

s3, when judging that the relevant records stored in the database exist, further judging whether the relevant records have a first record with a version number of a default value, and when judging that the first record does not exist, directly storing the updated record into the database;

s4, when the first record is judged to exist, the version number of the first record is modified and locked according to a first preset rule, and then the updated record is directly stored into a database;

s5, after the updated record is stored in the database, using the first version identification of the updated record as a matching identification, judging whether a second record with preset conflict between the first version identification and the matching identification exists in the related record, and when judging that the second record does not exist, keeping the corresponding version number of the updated record as a default value and classifying the updated record into the related record range;

and S6, when the second record exists, modifying and locking the version number of the updated record according to a second preset rule, and then classifying the updated record into a related record range.

Further, the step S4 further includes:

when judging that the first record exists, further judging whether a preset conflict exists between the first version identifier of the first record and the first version identifier of the updated record, and when judging that the preset conflict does not exist, modifying and locking the version number of the first record according to a first preset rule, and directly storing the updated record into a database;

and when the preset conflict exists, keeping the version number corresponding to the first record as a default value, modifying and locking the version number of the updated record according to a second preset rule, and then storing the version number into the database.

Further, the first preset rule includes:

acquiring all second version identifications corresponding to the related records;

identifying the maximum value of the locked version number in the current second version identification;

and adding a preset version number stepping value as a new version number to replace the original default value according to the maximum value of the locked version number in the current second version identification.

Further, the preset conflict comprises a fixed update date mismatch and/or an update information mismatch, wherein the update information mismatch comprises a record operation user mismatch.

Further, the second preset rule includes:

and replacing the original default value with a new version number according to an indication code correspondingly set according to the preset conflict type.

Further, the version number is an integer; the default value is 0; the step value is 1.

The invention also relates to a version control system based on version number association dynamic configuration, which is characterized by comprising the following steps:

the updating record preprocessing module is used for adding a first version identifier and a second version identifier to the updating record;

the database retrieval module is used for retrieving the database according to the updated record name and judging whether the related record stored in the database exists or not;

the first judging module is used for judging whether a first record with the version number as a default value exists in the related records;

the second judging module is used for judging whether a second record with a preset conflict between the first version identifier and the matching identifier exists in the related records or not;

the version number management module is used for modifying the corresponding version number of the record;

and the data storage module is used for updating and storing the data records.

The invention also relates to a computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the above-mentioned method.

The invention also relates to an electronic device, which is characterized by comprising a processor and a memory;

the memory is used for storing a first version identification and a second version identification;

the processor is used for executing the method by calling the first version identification and the second version identification.

The invention also relates to a computer program product comprising a computer program and/or instructions, characterized in that the computer program and/or instructions, when executed by a processor, implement the steps of the above-mentioned method.

The beneficial effects of the invention are as follows:

by adopting the version control method and the version control system based on version number association dynamic configuration, the multi-version storage of the service data is realized based on the relational database, the multi-version record is realized by adding the integer type field as the version number and changing the value of the version number of the service data when the service data is newly added or updated each time, the huge cost brought by the encapsulation of a version control system is avoided, and compared with the encapsulation of the version control system, the method and the system have the advantages of low cost, high performance and good maintainability, and are far lower than the encapsulation of a set of powerful version control system in terms of learning cost and development and maintenance cost.

Drawings

Fig. 1 is a schematic flow chart of a version control method based on version number association dynamic configuration according to the present invention.

Fig. 2 is a schematic diagram of a version control system based on version number association dynamic configuration according to the present invention.

Detailed Description

For a clearer understanding of the contents of the present invention, reference will be made to the accompanying drawings and examples.

The first aspect of the present invention relates to a version control method based on version number association dynamic configuration, which has a step flow shown in fig. 1, and includes:

s1, acquiring an update record, and adding a first version identifier and a second version identifier to the update record; the first version identification comprises fixed updating date and updating information of the corresponding updating record; the second version identification includes a version number preset as a default value.

The version number is a mark which is independently established and used for indicating the version change relationship among the records, and can be preferably represented by an integer number so as to simplify the execution process of the method. Meanwhile, the default value actually represents the current latest version record, or the version record in the process, and may preferably be 0 (or any specific value not multiplexed). For version alternation, positive integer mode recording can be adopted, and the larger the version number value is, the newer the corresponding recording version is.

And S2, searching the database according to the name of the updated record, judging whether the related record stored in the database exists or not, and directly storing the updated record into the database when judging that the related record stored in the database does not exist.

In such cases, the oldest record version in a group of records is typically used, at which point the record can be directly saved and used as the associated record for a subsequent updated version.

And S3, when judging that the related records stored in the database exist, further judging whether the related records have a first record with a version number of a default value, and when judging that the first record does not exist, directly storing the updated record into the database.

For the case that the relevant records already exist in the database, at this time, the relevant record condition needs to be correspondingly judged first. Typically, there will be a version record in the associated record that is newer before the updated record, with its version number being retained as a default value. However, in some special data processing cases, there may be a case where the version number is not a default value in the relevant record, for example, the version number is specified to be modified, and at this time, the updated record may be directly reserved as the latest version with the default value version number.

And S4, when the first record exists, directly storing the updated record into the database after modifying and locking the version number of the first record according to the first preset rule.

In particular, when the first record exists, it is preferable to first determine the update record attribute using the first version flag and identify the version update attribute. Specifically, when the first record is judged to exist, whether a preset conflict exists between the first version identifier of the first record and the first version identifier of the updated record is further judged, and when the preset conflict does not exist, the version number of the first record is modified and locked according to a first preset rule, and then the updated record is directly stored in a database; and when the preset conflict exists, keeping the version number corresponding to the first record as a default value, modifying and locking the version number of the updated record according to a second preset rule, and then storing the version number into the database.

Through the operation, the update record can be correctly recorded, the data content is updated according to the update record, meanwhile, the original related record cannot be used due to the addition of the update record, the version number is dynamically adjusted according to a first preset rule automatically according to the version identification condition after the addition of the update record, and the association relation between different version records is clear and knowable.

Preferably, the first preset rule may include: acquiring all second version identifications corresponding to the related records; identifying the maximum value of the locked version number in the current second version identification; and adding a preset version number stepping value (for example, directly adding 1 to the version number of the new version) according to the maximum value of the locked version number in the current second version identification to be used as a new version number to replace the original default value.

The first preset rule is a processing mode of the version number between the records based on the definition of the version relation between the updated record and the related record. In fact, the user may represent the versioning relationship between the updated records in any applicable manner, and this embodiment is used to illustrate the implementation manner of the first preset rule in one possible manner, but not to limit the versioning rule completely.

And S5, after the updated record is stored in the database, using the first version identification of the updated record as a matching identification, judging whether a second record with preset conflict between the first version identification and the matching identification exists in the related record, and when judging that the second record does not exist, keeping the corresponding version number of the updated record as a default value and classifying the updated record into the related record range.

The preset conflict is a verification mode for consistency and rationality of records among different versions, and preferably verification is performed through the first version identification. Since the first version identifier does not change after being added to the corresponding record, the first version identifier can be used for performing operations such as verification and matching on the inherent attribute of the corresponding record.

Preferably, the preset conflict may include a fixed update date mismatch and/or an update information mismatch, and particularly, the update information mismatch item may include a record operation user mismatch. The fixed update date is an update time node record specific to the corresponding record, and may be a modification start time, a modification end time or an upload time of the version record. Because the fixed update dates of all records are unique, when abnormal conditions that different records contain the same fixed update date or the fixed update date of an update record is earlier than that of a related record exist, the current version update can be considered to have some unreasonable or potential errors, and therefore the user can be prompted through a special version number. Similarly, for the update information, for example, the record operation user, if the judgment result of coming and going with the expected situation appears, the update record can be considered to have some doubts, and the user needs to be specially prompted.

And S6, when the second record is judged to exist, modifying and locking the version number of the updated record according to a second preset rule, and then classifying the updated record into a related record range.

Unlike the first preset rule, the second preset rule is not used to satisfy the version change relationship between the updated record and the related record, but is used to prompt the problem that the updated record may have. Preferably, the second preset rule may implement specific labeling of the updated record by using an indicator code set correspondingly according to the preset conflict type as a new version number to replace an original default value.

Another aspect of the present invention further relates to a version control system dynamically configured based on version number association, whose structure is shown in fig. 2, including:

the first judging module is used for judging whether a first record with the version number as a default value exists in the related records or not;

the second judging module is used for judging whether a second record with preset conflict between the first version identifier and the matching identifier exists in the related records or not;

and the data storage module is used for updating and storing the data records.

By using this system, the above-described arithmetic processing method can be executed and a corresponding technical effect can be achieved.

An embodiment of the present invention further provides a computer-readable storage medium capable of implementing all the steps of the method in the above embodiment, wherein the computer-readable storage medium has a computer program stored thereon, and the computer program, when executed by a processor, implements all the steps of the method in the above embodiment.

Embodiments of the present invention further provide an electronic device for executing the method, as an implementation apparatus of the method, the electronic device at least has a processor and a memory, and particularly, the memory stores data required for executing the method and related computer programs, such as a first version identifier and a second version identifier, and the like, and executes all steps of implementing the method by using the data and the programs in the memory and calling the processor, and obtaining corresponding technical effects.

Preferably, the electronic device may comprise a bus architecture, which may include any number of interconnected buses and bridges that link together various circuits, including one or more processors and memory. The bus may also link various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter may be the same element, i.e., a transceiver, providing a means for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory may be used for storing data used by the processor in performing operations.

Additionally, the electronic device may further include a communication module, an input unit, an audio processor, a display, a power source, and the like. The processor (or controller, operational controls) employed may include a microprocessor or other processor device and/or logic device that receives input and controls the operation of various components of the electronic device; the memory may be one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices, and may store the above-mentioned related data information, and may also store a program for executing the related information, and the processor may execute the program stored in the memory to realize information storage or processing, etc.; the input unit is used for providing input to the processor, and can be a key or a touch input device; the power supply is used for supplying power to the electronic equipment; the display is used for displaying display objects such as images and characters, and may be an LCD display, for example. The communication module is a transmitter/receiver that transmits and receives signals via an antenna. The communication module (transmitter/receiver) is coupled to the processor to provide an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal. Based on different communication technologies, a plurality of communication modules, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be disposed in the same electronic device. The communication module (transmitter/receiver) is also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and receive audio input from the microphone to implement the usual telecommunication functions. The audio processor may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor is also coupled to the central processor, so that recording on the local machine can be performed through the microphone, and sound stored on the local machine can be played through the loudspeaker.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a system for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A version control method based on version number association dynamic configuration is characterized by comprising the following steps:

2. The method of claim 1, wherein the step S4 further comprises:

when the first record is judged to exist, further judging whether a preset conflict exists between the first version identification of the first record and the first version identification of the updated record, and when the preset conflict does not exist, modifying and locking the version number of the first record according to a first preset rule, and directly storing the updated record into a database;

3. The method of claim 1 or 2, wherein the first preset rule comprises:

4. The method of claim 1 or 2, wherein the preset conflict comprises a fixed update date mismatch and/or an update information mismatch, wherein the update information mismatch comprises a record operation user mismatch.

5. The method of claim 4, wherein the second preset rule comprises:

6. The method of claim 3, wherein the version number is an integer; the default value is 0; the step value is 1.

7. A version control system dynamically configured based on version number association, comprising:

the database retrieval module is used for retrieving the database according to the name of the updated record and judging whether the related record stored in the database exists or not;

and the data storage module is used for updating and storing the data records.

8. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 6.

9. An electronic device comprising a processor and a memory;

the processor, configured to execute the method of any one of claims 1 to 6 by calling the first version identification and the second version identification.

10. A computer program product comprising a computer program and/or instructions, characterized in that the computer program and/or instructions, when executed by a processor, implement the steps of the method of any one of claims 1 to 6.