CN114579180A - Data migration method and device, electronic equipment and storage medium - Google Patents

Abstract

The present disclosure relates to a method, apparatus, electronic device and storage medium for data migration, and relates to the field of software. First, the audit status of the target version of the target program is obtained; then, if the audit status of the target version is passed, the interface change status of the data interface of the target program is obtained; the interface change status represents the target When the data interface of the program is changed from the first interface to the second interface, the program data corresponding to the current version is migrated from the database corresponding to the current version to the database corresponding to the target version. Through the above solution, when the interface change state of the data interface of the target program changes, the program data of the current version can be migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience. .

Description

Method, device, electronic device and storage medium for data migration

technical field

The present disclosure relates to the field of software, and in particular, to a data migration method, apparatus, electronic device, and storage medium.

Background technique

With the development of Internet technology, the iterative update speed of software versions has been accelerated, and the software compatibility problems of different versions caused by the iterative update of software versions have become increasingly prominent. If the data interface of the current version is changed, the program data of the current version cannot be migrated to the database of the target version in time, which may cause the program data of the current version to be lost or inconvenient to access, affecting the user experience.

For example, in the case of e-commerce software using mini-programs, when the operator of the e-commerce software releases a new mini-program template and the data interface of the new mini-program template is changed, the program data of the current version cannot interface with the new data Compatible, it may cause the order data of the current version to be unable to be migrated to the database of the new version in time, which may result in the loss or inaccessibility of the order data, affecting the user experience.

SUMMARY OF THE INVENTION

In order to overcome the problems existing in the related art, the present disclosure provides a data migration method, apparatus, electronic device and storage medium.

According to a first aspect of the embodiments of the present disclosure, there is provided a method for data migration, the method comprising:

Obtain the audit status of the target version of the target program; the target version is an updated version of the current version of the target program;

Obtain the interface change state of the data interface of the target program when the audit status of the target version is passed;

When the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface, the program data corresponding to the current version is migrated from the database corresponding to the current version to the target version The corresponding database; the first interface is the target program, the data interface between the database corresponding to the current version, the second interface is the target program, and the database corresponding to the target version. data interface.

Optionally, migrating the program data corresponding to the current version from the database corresponding to the current version to the database corresponding to the target version includes:

acquiring the data migration state of the program data corresponding to the current version, where the data migration state represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version;

When the data migration state is not migrated, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process.

Optionally, the process of migrating the program data from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process includes:

Obtain the preset data mapping relationship between the first interface and the second interface of the target program;

The program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process according to the preset data mapping relationship.

Optionally, the method further includes:

After the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the data migration state of the program data corresponding to the current version is changed to migrated.

Optionally, the method further includes:

Determine a service version according to the audit status of the target version of the target program;

The interface of the service version is displayed to the user, so as to provide the user with the service with the service version.

Optionally, the determining a service version according to the audit status of the target version of the target program includes:

In the case that the review status of the target version of the target program is under review or failed, the current version of the target program is used as a service version; or,

When the audit status of the target version of the target program is passed, the target version of the target program is used as a service version.

According to a second aspect of the embodiments of the present disclosure, there is provided an apparatus for data migration, the apparatus comprising:

The first acquisition module is configured to acquire the audit status of the target version of the target program; the target version is an updated version of the current version of the target program;

a second acquisition module, configured to acquire the interface change status of the data interface of the target program when the audit status of the target version is passed;

The data migration module is configured to change the program data corresponding to the current version from the program data corresponding to the current version to the data interface corresponding to the current version when the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface. The database is migrated to the database corresponding to the target version; the first interface is the target program, a data interface between the database corresponding to the current version, and the second interface is the target program, which is the same as the target program. The data interface between the databases corresponding to the target version.

Optionally, the data migration module is further configured to:

acquiring the data migration state of the program data corresponding to the current version, where the data migration state represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version;

When the data migration state is not migrated, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process.

Optionally, the data migration module is further configured to:

Obtain the preset data mapping relationship between the first interface and the second interface of the target program;

The program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process according to the preset data mapping relationship.

Optionally, the data migration module is further configured to:

After the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the data migration state of the program data corresponding to the current version is changed to migrated.

Optionally, the device further includes:

The service module is configured to determine a service version according to the audit status of the target version of the target program; and display an interface of the service version to a user, so as to provide a service for the user with the service version.

Optionally, the service module is further configured to:

In the case that the review status of the target version of the target program is under review or failed, the current version of the target program is used as a service version; or,

When the audit status of the target version of the target program is passed, the target version of the target program is used as a service version.

According to a third aspect of the embodiments of the present disclosure, there is provided an electronic device, the electronic device comprising:

a memory on which a computer program is stored;

A processor, configured to execute the computer program in the memory, to implement the steps of the method in any one of the above-mentioned first aspect.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, implements the steps of the method described in the first aspect.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

The present disclosure first obtains the audit status of the target version of the target program; then, when the audit status of the target version is passed, obtains the interface change status of the data interface of the target program; When the data interface of the target program is changed from the first interface to the second interface, the program data corresponding to the current version is migrated from the database corresponding to the current version to the database corresponding to the target version. Through the above solution, when the interface change state of the data interface of the target program changes, the program data of the current version can be migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience. .

It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure, and together with the description, serve to explain the principles of the disclosure, but not to limit the disclosure.

Fig. 1 is a flow chart of a data migration method according to an exemplary embodiment.

Fig. 2 is a logic diagram of related parties of a target program according to an exemplary embodiment.

Fig. 3 is a flow chart of another data migration method according to an exemplary embodiment.

Fig. 4 is a flow chart of yet another data migration method according to an exemplary embodiment.

Fig. 5 is a flow chart of yet another data migration method according to an exemplary embodiment.

Fig. 6 is a flow chart of yet another data migration method according to an exemplary embodiment.

Fig. 7 is a block diagram of an apparatus for data migration according to an exemplary embodiment.

Fig. 8 is a block diagram of another apparatus for data migration according to an exemplary embodiment.

Fig. 9 is a block diagram of an electronic device according to an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numerals in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure, as recited in the appended claims, it being understood that the specific embodiments described herein are for illustration and explanation only The present disclosure is not intended to limit the present disclosure.

It should be noted that all the actions of obtaining signals, information or data in this application are carried out under the premise of complying with the corresponding data protection regulations and policies of the local country and with the authorization of the corresponding device owner.

First, the application scenarios of the present disclosure are explained. With the development of Internet technology, the iteration speed of software versions is accelerated, and the software compatibility problem caused by the iterative update of software versions has become increasingly prominent. The inventor found that different users have different preferences for software versions. , For example, in e-commerce applet software, the operator can release new applet templates, such as supporting new functions such as seckill and group purchase. After the software version is switched, the data interface corresponding to the target version of the target program may change. For example, due to the addition of new functions such as seckill and group purchase, the data interface of the order data adds a seckill price field. When the data interface of the target program changes, if the program data corresponding to the current version cannot be migrated to the database corresponding to the target version in time, the program data of the current version may be lost or inconvenient to access, affecting the user experience.

To this end, the present disclosure provides a data migration method, apparatus, electronic device, and storage medium. When the interface of the data interface of the target program is changed, the program data of the current version can be migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience.

The present disclosure will be described below with reference to specific embodiments.

FIG. 1 is a flowchart of a method for data migration according to an exemplary embodiment. As shown in FIG. 1 , the method may include the following steps:

In step S101, the audit status of the target version of the target program is acquired.

The target version may be an updated version of the current version of the target program, and the review status may include passed, failed, and under review.

In Internet applications, the release of the target version of the target program usually needs to be reviewed by the platform side, which can be the application store platform side or the basic business platform side, such as chat applet platform, payment applet platform, etc. This disclosure does not limit this. Fig. 2 is a logic diagram of related parties of a target program according to an exemplary embodiment. As shown in Fig. 2, the application party is the decider of the service version of the target program, and can change the target program's service version according to its own software requirements. The target version is submitted to the platform for review. After passing the platform's review, the target version of the target program can be used to provide services to end users. The target version of the above target program may be provided by the operator, or may be obtained and generated from other channels, which is not limited in the present disclosure. For example, in an e-commerce application, the application side as an e-commerce merchant can apply the applet template provided by the operator to generate the target version of the target program and submit it to the platform side for review, or use a third-party applet template or secondary development to generate the target program. The target version of the target program is submitted to the platform party for review, which is not limited in this disclosure. Optionally, the relevant parties of the target program may also include operators, such as the e-commerce platform in the e-commerce application, which can manage the e-commerce platform. You can also publish target version templates of target programs (such as mini-program templates) to e-commerce merchants to improve the profitability of e-commerce merchants.

In step S102, if the audit status of the target version is passed, the interface change status of the data interface of the target program is acquired.

When the audit status of the target version is passed, the target version can be used to provide services to users. In some possible implementations, the target version can be obtained through the preset Release notes of the target version. The program's data interface changes state.

For example, in an e-commerce application, a seckill module is added to the target version. When the approval status of the target version submitted by a merchant serving as the application party is passed, when the end user opens the merchant's interface, The interface of the target version will be displayed, that is, it can provide the newly added seckill function. Correspondingly, in the data interface of the target program, a seckill price field can be added to the order data table to record the price of transactions through seckill in the order. information. The data interface change status of the target program can be obtained through the preset version description of the target version.

In step S103, when the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface, the program data corresponding to the current version is migrated from the database corresponding to the current version to the database corresponding to the target version.

Wherein, the first interface is the data interface between the target program and the database corresponding to the current version, and the second interface is the data interface between the target program and the database corresponding to the target version.

In this way, through the above solution, when the interface change state of the data interface of the target program changes, the program data of the current version can be migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience. experience.

FIG. 3 is a flowchart of step S103 according to the embodiment shown in FIG. 1 . As shown in FIG. 3 , in an embodiment, the steps of step S103 may include the following steps:

In step S1031, the data migration state of the program data corresponding to the current version is acquired.

The data migration state represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version.

In a possible implementation manner, the data migration state of the program data corresponding to the current version may be obtained through a preset data migration state.

For example, in an e-commerce application, after the e-commerce merchant as the application party submits the target version of the target program for review, the preset data migration status corresponding to the e-commerce merchant is changed to not migrated, indicating that the e-commerce merchant is sending the data to The platform side submitted the target version of the target program for review, and the program data of the target program has not been migrated.

In step S1032, when the data migration state is not migrated, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process.

The asynchronous data migration indicates that the normal use of the target program is not affected during the data migration process.

For example, in an e-commerce application, when the approval status of the target version is passed, the display interface of the newly accessed terminal user is the interface of the target version. The terminal user who has accessed will receive a prompt of version change, and in response to the user's operation, the display interface of the terminal user who has accessed will be switched to the target version. The program data generated by the end user through the interface of the target version is stored in the database corresponding to the target version through the second interface of the target version.

In some possible implementations, the program data can be migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process through the following steps.

Step 1: Obtain the preset data mapping relationship between the first interface and the second interface of the target program.

In some possible implementation manners, the preset data mapping relationship may be obtained from the release notes (Release notes) of the target version.

The preset data mapping relationship may reflect the field mapping relationship between the first interface and the second interface.

For example, in an e-commerce application, the target version of the target program adds a seckill module, and adds a seckill price in the order management table, and the data mapping relationship may include the field mapping relationship described in Table 1.

first interface order number product name commodity price quantity transaction price total transaction price payment method second interface order number product name commodity price Lightning strike price quantity transaction price total transaction price payment method

Table 1

As shown in Table 1, the seckill price in the second interface is a newly added field, and the rest are in a one-to-one correspondence.

Further, the preset data mapping relationship may also reflect the corresponding relationship between the value spaces in the corresponding fields of the first interface and the second interface.

For example, in an e-commerce application, the value space of some fields of the second interface has changed compared with that of the first interface, and the data mapping relationship may include the value space mapping relationship described in Table 2.

field first interface second interface payment method 0-payment method 1, 1-payment method 2, 2-payment method 3 100 - Payment method 1, 101 - Payment method 2, 102 - Payment method 3, 103 - Payment method 4

Table 2

As shown in Table 2, the value space of the payment method fields corresponding to the first interface and the second interface has changed, and the first interface is [0,1,2]. The second interface is [100, 101, 102, 103], and a new payment method is added to the second interface.

It should be noted that Table 1 and Table 2 only provide examples of data mapping relationships, which are not limited in the present disclosure.

Step 2: Migrate the program data from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process according to the preset data mapping relationship.

After acquiring the preset data mapping relationship, the asynchronous data migration process can migrate program data from the database corresponding to the current version to the database corresponding to the target version according to the preset data mapping relationship.

In some possible implementations, the asynchronous data migration process can be implemented through hyperf (a high-performance PHP microservice framework) and Swoole (PHP asynchronous network communication engine), and multiple asynchronous data migration processes can be implemented through Rabbitmq (message-oriented middleware). ), for details, please refer to the description in the related art, which will not be repeated here.

FIG. 4 is a flowchart of another step S103 according to the embodiment shown in FIG. 1. As shown in FIG. 4, in an embodiment, the steps of step S103 may further include the following steps:

In step S1033, after the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the data migration status of the program data corresponding to the current version is changed to migrated.

For example, in an e-commerce application, after the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the preset data migration state corresponding to the e-commerce merchant is changed to migrated. . It is avoided that the asynchronous data migration process repeatedly migrates program data from the database corresponding to the current version to the database corresponding to the target version, thereby causing duplicate data or data conflicts.

Through the above solution, when the interface change state of the data interface of the target program is changed, the program data of the current version can be migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience. experience.

FIG. 5 is a flowchart of a method for data migration according to an exemplary embodiment. As shown in FIG. 5 , the method may further include the following steps:

In step S104, the service version is determined according to the audit status of the target version of the target program.

For example, in an e-commerce application, the merchant is the decider of the service version of the target program, and can determine the service version of the target program based on software requirements. Merchants with many categories and aggressive promotions are keen to adopt the target version to meet the needs of business marketing. , and merchants with few categories and little change in product demand think that the current version meets the demand, and are unwilling to frequently update the target version. The application side can submit the target version of the target program to the platform side for review according to its own software requirements. For merchants who are not willing to use the target version, they can continue to use the current version as the service version without submitting the target version of the target program for review.

In some possible implementations, the service version can be determined according to the audit status of the target version of the target program in the following manner.

Mode 1: In the case that the audit status of the target version of the target program is under review or failed, the current version of the target program is used as the service version.

For example, in an e-commerce application, when the target version of the target program submitted by the merchant has not passed the review or the review result is that the target version has failed, the current version of the target program is used as the service version.

Mode 2: When the audit status of the target version of the target program is passed, the target version of the target program is used as the service version.

For example, in an e-commerce application, if the approval status of the target version of the target program submitted by the merchant is passed, the target version of the target program is used as the service version.

In step S105, the interface of the service version is displayed to the user, so as to provide the user with a service with the service version.

The user can be the end user shown in FIG. 2 , such as a consumer in an e-commerce application, who submits an order through the interface of the service version to complete shopping, or can be an application party shown in FIG. 2 , such as a merchant in an e-commerce application , through the interface of the service version to complete the daily operation, or the operator shown in Figure 2, such as the e-commerce platform in the e-commerce application, through the interface of the service version to complete the management of multiple merchants, or to release new target programs. The target version template (for example, the applet template), which is used by the application party to download the target version template and generate the target version.

Through the above solution, the service version can be determined according to the audit status of the target version of the target program, so as to meet the version requirements of different users, improve the compatibility of the target program, and improve the user experience.

Fig. 6 is a flow chart of yet another data migration method according to an exemplary embodiment. As shown in Fig. 6 , the method may include the following steps:

In step S601, the audit status of the target version of the target program is acquired.

The target version may be an updated version of the current version of the target program, and the review status may be passed, failed, and under review.

In step S602, the interface change status of the data interface of the target program is acquired.

When the audit status of the target version is passed, obtain the interface change status of the data interface of the target program.

In some possible implementation manners, the change status of the data interface of the target program may be obtained through the preset release notes (Releasenotes) of the target version. For a specific description, refer to the description of step S102, which will not be repeated here.

In step S603, the data migration state of the program data corresponding to the current version is acquired.

The data migration state represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version.

When the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface, the data migration state of the program data corresponding to the current version can be obtained through the preset data migration state.

For example, in an e-commerce application, after the e-commerce merchant as the application party submits the target version of the target program for review, the preset data migration status corresponding to the e-commerce merchant is changed to not migrated, indicating that the e-commerce merchant is sending the data to The platform side submitted the target version of the target program for review, and the program data of the target program has not been migrated.

In step S604, a preset data mapping relationship between the first interface and the second interface of the target program is acquired.

The preset data mapping relationship may reflect the field mapping relationship between the first interface and the second interface. In some possible implementations, the preset data mapping relationship may be obtained from the release notes (Releasenotes) of the target version.

When the data migration state is not migrated, the preset data mapping relationship between the first interface and the second interface of the target program is acquired. The preset data mapping relationship may reflect the field mapping relationship between the first interface and the second interface. Further, the preset data mapping relationship may also reflect the corresponding relationship between the value spaces in the corresponding fields of the first interface and the second interface, which is not limited in the present disclosure.

In step S605, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process according to the preset data mapping relationship.

After acquiring the preset data mapping relationship, the asynchronous data migration process can migrate program data from the database corresponding to the current version to the database corresponding to the target version according to the preset data mapping relationship.

In step S606, the data migration status of the program data corresponding to the current version is changed to migrated.

For example, in an e-commerce application, after the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the preset data migration state corresponding to the e-commerce merchant is changed to migrated. . It is avoided that the asynchronous data migration process repeatedly migrates program data from the database corresponding to the current version to the database corresponding to the target version, thereby causing duplicate data or data conflicts.

In step S607, the target version of the target program is taken as the service version.

If the audit status of the target version is passed, the target version of the target program is regarded as the service version.

In step S608, the current version of the target program is taken as the service version.

In the case that the review status of the target version is failed or under review, the current version of the target program is regarded as the service version.

In step S609, the interface of the service version is displayed to the user, so as to provide services for the user with the service version.

The user can be the end user shown in FIG. 2 , such as a consumer in an e-commerce application, who submits an order through the interface of the service version to complete shopping, or can be an application party shown in FIG. 2 , such as a merchant in an e-commerce application , through the interface of the service version to complete the daily operation, or the operator shown in Figure 2, such as the e-commerce platform in the e-commerce application, through the interface of the service version to complete the management of multiple merchants, or to release new target programs. The target version template (for example, the applet template), which is used by the application party to download the target version template and generate the target version.

Through the above solution, the service version can be determined according to the audit status of the target version of the target program, the version requirements of different users can be met, the compatibility of the target program can be improved, and the interface change status of the data interface of the target program can be changed. In this case, the program data of the current version is migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience.

FIG. 7 is a block diagram of a data migration apparatus according to an exemplary embodiment. As shown in FIG. 7 , the data migration apparatus 700 includes:

The first obtaining module 701 is configured to obtain the audit status of the target version of the target program; the target version is an updated version of the current version of the target program;

The second acquisition module 702 is configured to acquire the interface change status of the data interface of the target program when the audit status of the target version is passed;

The data migration module 703 is configured to migrate the program data corresponding to the current version from the database corresponding to the current version to the data interface corresponding to the target version when the interface change state represents that the data interface of the target program is changed from the first interface to the second interface. database; the first interface is the target program, the data interface between the database corresponding to the current version, and the second interface is the target program, the data interface between the database corresponding to the target version.

Optionally, the data migration module 703 is further configured to:

Obtain the data migration status of the program data corresponding to the current version, and the data migration status represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version;

When the data migration state is not migrated, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process.

Optionally, the data migration module 703 is further configured to:

Obtain the preset data mapping relationship between the first interface and the second interface of the target program;

The program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process according to the preset data mapping relationship.

Optionally, the data migration module 703 is further configured to:

After the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the data migration state of the program data corresponding to the current version is changed to migrated.

FIG. 8 is a block diagram of a data migration apparatus according to an exemplary embodiment. As shown in FIG. 8 , the data migration apparatus 700 further includes:

The service module 704 is configured to determine the service version according to the audit status of the target version of the target program; and display the interface of the service version to the user, so as to provide services for the user with the service version.

Optionally, the service module 704 is further configured to:

If the audit status of the target version of the target program is under review or failed, the current version of the target program is used as the service version; or,

When the approval status of the target version of the target program is passed, the target version of the target program is regarded as the service version.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Through the above solution, the service version can be determined according to the audit status of the target version of the target program, the version requirements of different users can be met, the compatibility of the target program can be improved, and the interface change status of the data interface of the target program can be changed. In this case, the program data of the current version is migrated to the database corresponding to the target version, so as to ensure the integrity of the program data of the target program and improve the user experience.

FIG. 9 is a block diagram of an electronic device 900 according to an exemplary embodiment. As shown in FIG. 9 , the electronic device 900 may include: a processor 901 and a memory 902 . The electronic device 900 may also include one or more of a multimedia component 903 , an input/output (I/O) interface 904 , and a communication component 905 .

The processor 901 is configured to control the overall operation of the electronic device 900 to complete all or part of the steps in the above-mentioned data migration method. The memory 902 is used to store various types of data to support operations on the electronic device 900, such data may include, for example, instructions for any application or method operating on the electronic device 900, and application-related data, Such as contact data, messages sent and received, pictures, audio, video, and so on. The memory 902 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random Access Memory, SRAM for short), electrically erasable programmable read-only memory ( Electrically Erasable Programmable Read-Only Memory (EEPROM for short), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), read-only Memory (Read-Only Memory, ROM for short), magnetic memory, flash memory, magnetic disk or optical disk. Multimedia components 903 may include screen and audio components. The screen can be, for example, a touch screen, and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in memory 902 or transmitted through communication component 905 . The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 904 provides an interface between the processor 901 and other interface modules, and the above-mentioned other interface modules may be a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons. The communication component 905 is used for wired or wireless communication between the electronic device 900 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or one or a combination of them , which is not limited here. Therefore, the corresponding communication component 905 may include: Wi-Fi module, Bluetooth module, NFC module and so on.

In another exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including program instructions, the program instructions implementing the steps of the above-mentioned data migration method when executed by a processor. For example, the computer-readable storage medium can be the above-mentioned memory 902 including program instructions, and the above-mentioned program instructions can be executed by the processor 901 of the electronic device 900 to complete the above-mentioned data migration method.

Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the present disclosure. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or techniques in the technical field not disclosed by the present disclosure . The specification and examples are to be regarded as exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise structures described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A method for data migration, wherein the method comprises: Obtain the audit status of the target version of the target program; the target version is an updated version of the current version of the target program; Obtain the interface change state of the data interface of the target program when the audit status of the target version is passed; When the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface, the program data corresponding to the current version is migrated from the database corresponding to the current version to the target version The corresponding database; the first interface is the target program, the data interface between the database corresponding to the current version, the second interface is the target program, and the database corresponding to the target version. data interface. 2. The method according to claim 1, wherein the migrating the program data corresponding to the current version from the database corresponding to the current version to the database corresponding to the target version comprises: acquiring the data migration state of the program data corresponding to the current version, where the data migration state represents whether the program data has been migrated from the database corresponding to the current version to the database corresponding to the target version; When the data migration state is not migrated, the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process. 3. The method according to claim 2, wherein the step of migrating the program data from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process comprises: Obtain the preset data mapping relationship between the first interface and the second interface of the target program; The program data is migrated from the database corresponding to the current version to the database corresponding to the target version through an asynchronous data migration process according to the preset data mapping relationship. 4. The method according to claim 2 or 3, wherein the method further comprises: After the program data is migrated from the database corresponding to the current version to the database corresponding to the target version through the asynchronous data migration process, the data migration state of the program data corresponding to the current version is changed to migrated. 5. The method according to claim 1, wherein the method further comprises: Determine a service version according to the audit status of the target version of the target program; The interface of the service version is displayed to the user, so as to provide the user with the service with the service version. 6. The method according to claim 5, wherein the determining a service version according to the audit status of the target version of the target program comprises: In the case that the review status of the target version of the target program is under review or failed, the current version of the target program is used as a service version; or, When the audit status of the target version of the target program is passed, the target version of the target program is used as a service version. 7. An apparatus for data migration, wherein the apparatus comprises: The first acquisition module is configured to acquire the audit status of the target version of the target program; the target version is an updated version of the current version of the target program; a second acquisition module, configured to acquire the interface change status of the data interface of the target program when the audit status of the target version is passed; The data migration module is configured to change the program data corresponding to the current version from the program data corresponding to the current version to the data interface corresponding to the current version when the interface change state indicates that the data interface of the target program is changed from the first interface to the second interface. The database is migrated to the database corresponding to the target version; the first interface is the target program, a data interface between the database corresponding to the current version, and the second interface is the target program, which is the same as the target program. The data interface between the databases corresponding to the target version. 8. The apparatus according to claim 7, wherein the apparatus further comprises: The service module is configured to determine a service version according to the audit status of the target version of the target program; and display an interface of the service version to a user, so as to provide a service for the user with the service version. 9. An electronic device, characterized in that, comprising: a memory on which a computer program is stored; A processor for executing the computer program in the memory to implement the steps of the method of any one of claims 1-6. 10. A non-transitory computer-readable storage medium on which computer program instructions are stored, characterized in that, when the program instructions are executed by a processor, the steps of the method of any one of claims 1-6 are implemented.

Images