CN111352918B - Terminal database data migration method and system - Google Patents
Terminal database data migration method and system Download PDFInfo
- Publication number
- CN111352918B CN111352918B CN201811571916.7A CN201811571916A CN111352918B CN 111352918 B CN111352918 B CN 111352918B CN 201811571916 A CN201811571916 A CN 201811571916A CN 111352918 B CN111352918 B CN 111352918B
- Authority
- CN
- China
- Prior art keywords
- database
- data
- class
- attribute type
- data table
- 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
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a terminal database data migration method, which comprises the following steps: if the database exists, receiving service data issued by the server; converting the business data into a class data model; checking whether a data table corresponding to the class data model exists in the database; if a data table corresponding to the class data model exists in the database, further checking whether the attribute type of the class data model is consistent with the attribute type of the database; when the attribute type of the class data model is inconsistent with the attribute type of the database, creating a new data table in the database, and migrating the data of the original data table in the database to the new data table. The invention also discloses a terminal database data migration system. The invention relates to the technical field of terminal operating systems and terminal databases, in particular to a terminal database data migration method and a terminal database data migration system, which realize automatic, real-time and silent migration of a terminal database, improve response time of software requirements and improve user experience.
Description
Technical Field
The invention relates to the technical field of terminal operating systems and terminal databases, in particular to a terminal database data migration method and a terminal database data migration system.
Background
In the existing software development field related to the terminal client (IOS/Android), there are demands for database data migration, for example, in the iterative development process of a software system, because new demands cause the attribute of a client (IOS/Android) data table to change (add/delete), a new data table needs to be created, then data of an old data table is migrated to the new data table, and meanwhile, the old data table is deleted and the new data table is modified to be the name of the old database.
Aiming at the existing first data migration method, when a new version client (IOS/Android) realizes data migration of a database, the user must wait for the update of the client (IOS/Android) before triggering the data migration of the database, so that the real-time data migration cannot be realized, and meanwhile, an old version client cannot trigger the data migration of the database, so that the new requirements and new functions of a software system cannot be experienced; for the existing second data migration method, when the hot repair restoration is used for realizing the data migration of the database, if the versions of the hot patches are too many, great performance overhead is required for the version management of the hot patches, meanwhile, the IOS operation system is forbidden to use a hot repair mechanism, and the Android operation system also forbids part of the capability of the hot repair principle in the newly released version, so that the method is inconvenient.
Disclosure of Invention
The present invention aims to solve at least one of the technical problems in the related art to some extent. To this end, an object of the present invention is to provide an automatic, real-time, silent migration method and system for terminal database,
the technical scheme adopted by the invention is as follows:
in a first aspect, the present invention provides a terminal database data migration method, including:
if the database exists, receiving service data issued by the server;
converting the service data into a class data model;
checking whether a data table corresponding to the class data model exists in the database;
if a data table corresponding to the class data model exists in the database, further checking whether the attribute type of the class data model is consistent with the attribute type of the database;
and when the attribute type of the class data model is inconsistent with the attribute type of the database, creating a new data table in the database, and migrating the data of the original data table in the database to the new data table.
As a further improvement of the above scheme, the method further includes creating a database if the database does not exist, and receiving service data issued by the server.
As a further improvement of the above solution, the converting the service data into a class data model specifically includes:
recursively and circularly analyzing the nesting relation of the service data, and establishing a attribution relation queue of a class data model;
circularly taking out an attribute list of the service data from the top of the attribution relation queue, generating a corresponding class data model by utilizing a dynamic runtime reflection mechanism, and further generating class definition and class files, wherein the class names of the classes use packet names of the service data, and the class files are added with fixed prefixes before the class names;
when a corresponding class data model is generated by utilizing a dynamic runtime reflection mechanism, the class data model generated in the last cycle is added as a sub-attribute of the current class data model.
As a further improvement of the above solution, the checking whether the data table corresponding to the class data model exists in the database specifically includes:
and recursively circulating to inquire whether a corresponding data table exists in the database through the class name and the subclass of the class data model.
As a further improvement of the above solution, after the step of checking whether the data table corresponding to the class data model exists in the database, the method further includes:
if the data table corresponding to the class data model does not exist in the database, converting the attribute type of the class data model into the attribute type of the database;
creating a data table SQL statement, and executing the creation of a new data table;
creating an insert SQL statement and performing the insertion of the business data.
As a further improvement of the above solution, after the step of further checking whether the attribute type of the class data model is consistent with the attribute type of the database if the data table corresponding to the class data model exists in the database, the method further includes:
and when the attribute type of the class data model is consistent with the attribute type of the database, creating an insertion SQL sentence, and executing insertion of the service data.
As a further improvement of the above solution, creating a new data table in the database when the attribute type of the class data model is inconsistent with the attribute type of the database, migrating data of an original data table in the database to the new data table, and deleting the original data table specifically includes:
when the attribute type of the class data model is inconsistent with the attribute type of the database, converting the attribute type of the class data model into the attribute type of the database, and creating a new data table in the database;
starting an asynchronous sub-thread and a database transaction, and migrating the data of an original data table in the database to the new data table;
and deleting the original data table in the database, and ending the asynchronous sub-thread and the database transaction.
In a second aspect, the present invention provides a terminal database data migration system, including:
the receiving module is used for receiving the service data issued by the server if the database exists;
the first conversion module is used for converting the service data into a class data model;
the first checking module is used for checking whether a data table corresponding to the class data model exists in the database;
the second checking module is used for further checking whether the attribute type of the class data model is consistent with the attribute type of the database if the data table corresponding to the class data model exists in the database;
and the migration module is used for creating a new data table in the database and migrating the data of the original data table in the database to the new data table when the attribute type of the class data model is inconsistent with the attribute type of the database.
As a further improvement of the above, the system further comprises:
the first creating module is used for creating the database and receiving the service data issued by the server if the database does not exist.
As a further improvement of the above, the system further comprises:
and the insertion module is used for creating an SQL sentence when the attribute type of the class data model is consistent with the attribute type of the database, and executing the insertion of the service data.
The beneficial effects of the invention are as follows:
according to the data migration method and system for the terminal database, when the terminal database exists, whether the data table corresponding to the class data model exists in the database is checked, whether the attribute type of the class data model is consistent with the attribute type of the database is checked, and then data migration is performed, so that the technical problems that in the prior art, the data migration of the database can be triggered after a user upgrades a client (IOS/Android) or the data migration of the database is forbidden by an official operating system through hot repair restoration are solved, the automatic, real-time and silent migration of the terminal database is realized, any service and scene are not needed, frequent upgrading of the version of the client (Android/IOS) caused by the change of the data table structure is reduced, the response time of software requirements is improved, and the user experience is improved.
Drawings
The following is a further description of embodiments of the invention, taken in conjunction with the accompanying drawings:
fig. 1 is a schematic flow chart of a terminal database data migration method according to a first embodiment of the present invention;
fig. 2 is a flow chart of a terminal database data migration method according to a second embodiment of the present invention;
fig. 3 is a block diagram of a terminal database data migration system according to a third embodiment of the present invention.
Detailed Description
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
Example 1
Fig. 1 is a schematic flow chart of a terminal database data migration method according to a first embodiment of the present invention, and referring to fig. 1, a terminal database data migration method includes steps S01 to S05.
S01, if the database exists, receiving service data issued by a server;
s02, converting the business data into a class data model;
s03, checking whether a data table corresponding to the class data model exists in the database;
s04, if a data table corresponding to the class data model exists in the database, further checking whether the attribute type of the class data model is consistent with the attribute type of the database;
s05, when the attribute type of the class data model is inconsistent with the attribute type of the database, creating a new data table in the database, and migrating the data of the original data table in the database to the new data table.
In this embodiment, the migration method further includes the steps of:
s00, if the database does not exist, creating the database, and receiving service data issued by the server.
In this embodiment, step S02 specifically includes:
s021, recursively and circularly analyzing the nesting relation of the service data, and establishing a attribution relation queue of the class data model;
s022, circularly taking out an attribute list of service data from the top of the attribution relation queue, generating a corresponding class data model by utilizing a dynamic runtime reflection mechanism, and further generating class definition and class files, wherein the class names of the classes use the registration of the service data, and the class files are added with fixed prefixes before the class names;
s023, when a corresponding class data model is generated by utilizing a dynamic runtime reflection mechanism, adding the class data model generated in the last cycle as a sub attribute of the current class data model.
In this embodiment, step S03 specifically includes:
and recursively circulating class names and subclasses of the same class data model, and inquiring whether a corresponding data table exists in a database.
In this embodiment, after step S03, the method further includes the steps of:
s06, if the data table corresponding to the class data model does not exist in the database, converting the attribute type of the class data model into the attribute type of the database;
s07, creating a data table SQL sentence, and executing the creation of a new data table;
s08, creating an insert SQL statement and executing insert business data.
In this embodiment, after step S04, the method further includes the steps of:
s09, when the attribute type of the class data model is consistent with the attribute type of the database, creating an insertion SQL sentence, and executing insertion business data.
In this embodiment, step S04 specifically includes:
if a data table corresponding to the class data model exists in the database, comparing the attribute name of the class data model with the attribute name of the database, and performing half-and-half comparison by using a dichotomy;
if the attribute names of the class data models are consistent with the attribute names of the databases, converting the attribute types of the class data models into the attribute types of the databases, further comparing the attribute class names of the class data models with the attribute class names of the databases, and checking whether the attribute class names of the class data models are consistent with the attribute class names of the databases.
In this embodiment, step S05 specifically includes:
s051, when the attribute type of the class data model is inconsistent with the attribute type of the database, converting the attribute type of the class data model into the attribute type of the database, and creating a new data table in the database;
s052, starting an asynchronous sub-thread and a database transaction, and migrating the data of an original data table in a database to a new data table;
s053, deleting the original data table in the database, and ending the asynchronous sub-thread and the database transaction.
Example two
Fig. 2 is a flow chart of a terminal database data migration method according to a second embodiment of the present invention, and referring to fig. 2, a terminal database data migration method includes steps S1 to S14.
Starting a terminal client;
s1, checking whether a database exists, if not, executing a step S2, and if so, executing a step S3;
s2, creating a database;
s3, receiving service data issued by a server;
s4, converting the business data into a class data model;
s5, checking whether a data table corresponding to the class data model exists in the database, if not, executing the step S6, and if so, executing the step S9;
s6, converting the attribute type of the class data model into the attribute type of the database;
s7, creating a data table SQL statement, and executing the creation of a new data table;
s8, creating an SQL sentence, executing the business data insertion, and ending the flow;
s9, checking whether the attribute type of the class data model is consistent with the attribute type of the data table, if so, executing the step S8, and if not, executing the step S10;
s10, converting the attribute type of the class data model into the attribute type of a database;
s11, creating a new data table;
s12, starting an asynchronous sub-thread and a database transaction;
s13, migrating the data of the original data table in the database to a new data table;
s14, deleting the original data table in the database, ending the asynchronous sub-thread and the database transaction, and ending the process.
In this embodiment, step S1 specifically includes: and checking whether the database exists by using the package name of the client, if not, executing the step S2, and if so, executing the step S3.
In this embodiment, step S2 specifically includes: creating a database by using the package name of the client;
in this embodiment, step S3 specifically includes:
s31, recursively and circularly analyzing the nesting relation of the service data, and establishing a attribution relation queue of the class data model;
s32, circularly taking out an attribute list of service data from the top of the attribution relation queue, generating a corresponding class data model by utilizing a dynamic runtime reflection mechanism, including writing class data model attributes by utilizing a dynamic runtime mechanism, class polymorphism, inheritance and the like of the class by utilizing a reflection means, and further generating class definition and class files by one-to-one correspondence, wherein the class names of the class use registration of the service data, and the class files are added with fixed prefixes on the basis of the class names;
s33, when a corresponding class data model is generated by utilizing a dynamic runtime reflection mechanism, adding the class data model generated in the last cycle as a sub-attribute of the current class data model.
In this embodiment, step S5 specifically includes: and (3) recursively circulating to check whether a data table corresponding to the class data model exists in the database through the class name and the subclass of the class data model, if not, executing the step S6, and if so, executing the step S9.
In this embodiment, step S6 specifically includes:
s61, establishing a formal expression (@ \ "[ a-zA-Z_0-9] + \" $), and screening the data type, the character string type and the object type in the class data model;
s62, establishing a corresponding relation between the class data model attribute and the database attribute, and respectively converting the class data model attribute and the database attribute into the attribute type in the data table by utilizing a dynamic runtime reflection mechanism.
In this embodiment, step S7 specifically includes: the recursion loops through the class names and their subclasses of the class data model to create a data table SQL statement in the database and performs the creation of a new data table.
In this embodiment, step S9 specifically includes:
s91, comparing the attribute names of the class data model with the attribute names of the database, and performing half-and-half comparison by using a dichotomy;
s92, if the attribute names of the class data models are consistent with the attribute names of the databases, converting the attribute types of the class data models into the attribute types of the databases, further comparing the attribute type names of the class data models with the attribute type names of the databases, checking whether the attribute type names of the class data models are consistent with the attribute type names of the databases, if so, executing the step S8, and if not, executing the step S10.
In this embodiment, step S12 is performed to prepare for data migration.
In this embodiment, step S13 specifically includes:
s131, the number of records of the original data table is circulated, and the records of the original data table are inserted into the new data table one by one;
s132, deleting the record of the original data table after the number of the records of the original data table is cycled.
In this embodiment, step S14 specifically includes: deleting the original data table in the database, renaming the new data table to be the name of the old data table, ending the asynchronous sub-thread and the database transaction, submitting the database, and ending the process.
According to the data migration method of the terminal database, when the terminal database exists, whether the data table corresponding to the class data model exists in the database is checked, whether the attribute type of the class data model is consistent with the attribute type of the database is checked, and then data migration is performed, so that the technical problem that the data migration of the database can be triggered only after a user upgrades a client (IOS/Android) or the data migration of the database is forbidden by an official operating system through hot repair restoration is solved, automatic, real-time and silent migration of the terminal database is realized, no service or scene is needed to be relied on, frequent upgrading of the version of the client (Android/IOS) caused by the change of the structure of the data table is reduced, the response time of software requirements is improved, and the user experience is improved.
Example III
Fig. 3 is a block diagram of a terminal database data migration system according to a third embodiment of the present invention, and referring to fig. 3, a terminal database data migration system includes:
the receiving module is used for receiving the service data issued by the server if the database exists;
the first conversion module is used for converting the business data into a class data model;
the first checking module is used for checking whether a data table corresponding to the class data model exists in the database;
the second checking module is used for further checking whether the attribute type of the class data model is consistent with the attribute type of the database if the data table corresponding to the class data model exists in the database;
and the migration module is used for creating a new data table in the database and migrating the data of the original data table in the database to the new data table when the attribute type of the class data model is inconsistent with the attribute type of the database.
In this embodiment, the migration system further includes:
the first creating module is used for creating the database and receiving the service data issued by the server if the database does not exist.
In this embodiment, the migration system further includes:
and the second conversion module is used for converting the attribute type of the class data model into the attribute type of the database if the data table corresponding to the class data model does not exist in the database.
In this embodiment, the migration system further includes:
and the second creation module is used for creating the SQL statement of the data table and executing the creation of the new data table.
In this embodiment, the migration system further includes:
the insertion module is used for creating an SQL sentence for insertion and executing the business data for insertion; the insertion module is also used for creating an insertion SQL sentence and executing insertion business data when the attribute type of the class data model is consistent with the attribute type of the database.
The terminal database data migration system provided in the third embodiment of the present invention is used for executing the terminal database data migration method in the first embodiment, and the working principles and the beneficial effects of the terminal database data migration system are in one-to-one correspondence, so that the description is omitted.
According to the data migration method and system for the terminal database, when the terminal database exists, whether the data table corresponding to the class data model exists in the database is checked, whether the attribute type of the class data model is consistent with the attribute type of the database is checked, and then data migration is performed, so that the technical problems that in the prior art, the data migration of the database can be triggered after a user upgrades a client (IOS/Android) or the data migration of the database is forbidden by an official operating system through hot repair restoration are solved, the automatic, real-time and silent migration of the terminal database is realized, any service and scene are not needed, frequent upgrading of the version of the client (Android/IOS) caused by the change of the data table structure is reduced, the response time of software requirements is improved, and the user experience is improved.
While the preferred embodiment of the present invention has been described in detail, the invention is not limited to the embodiment, and various equivalent modifications and substitutions can be made by one skilled in the art without departing from the spirit of the invention, and these equivalent modifications and substitutions are intended to be included in the scope of the present invention as defined in the appended claims.
Claims (8)
1. A method for migrating data in a terminal database, comprising:
if the database exists, receiving service data issued by the server;
converting the service data into a class data model;
checking whether a data table corresponding to the class data model exists in the database;
if a data table corresponding to the class data model exists in the database, further checking whether the attribute type of the class data model is consistent with the attribute type of the database;
when the attribute type of the class data model is inconsistent with the attribute type of the database, creating a new data table in the database, migrating the data of the original data table in the database to the new data table, and deleting the original data table;
the converting the service data into a class data model specifically comprises:
recursively and circularly analyzing the nesting relation of the service data, and establishing a attribution relation queue of a class data model;
circularly taking out an attribute list of the service data from the top of the attribution relation queue, generating a corresponding class data model by utilizing a dynamic runtime reflection mechanism, and further generating class definition and class files, wherein the class names of the classes use packet names of the service data, and the class files are added with fixed prefixes before the class names;
when a corresponding class data model is generated by utilizing a dynamic runtime reflection mechanism, adding the class data model generated in the last cycle as a sub-attribute of the class data model;
creating a new data table in the database when the attribute type of the class data model is inconsistent with the attribute type of the database, migrating the data of the original data table in the database to the new data table, and deleting the original data table specifically comprises:
when the attribute type of the class data model is inconsistent with the attribute type of the database, converting the attribute type of the class data model into the attribute type of the database, and creating a new data table in the database;
starting an asynchronous sub-thread and a database transaction, and migrating the data of an original data table in the database to the new data table;
and deleting the original data table in the database, and ending the asynchronous sub-thread and the database transaction.
2. The method for migrating terminal database data according to claim 1, further comprising creating a database if the database does not exist, and receiving service data issued by the server.
3. The method for migrating terminal database data according to claim 1, wherein said checking whether a data table corresponding to the class data model exists in the database comprises:
and recursively circulating to inquire whether a corresponding data table exists in the database through the class name and the subclass of the class data model.
4. A terminal database data migration method according to claim 3, further comprising, after said step of checking whether a data table corresponding to said class data model exists in said database:
if the data table corresponding to the class data model does not exist in the database, converting the attribute type of the class data model into the attribute type of the database;
creating a data table SQL statement, and executing the creation of a new data table;
creating an insert SQL statement and performing the insertion of the business data.
5. The method for migrating terminal database data according to claim 1, wherein after the step of further checking whether the attribute type of the class data model is consistent with the attribute type of the database if the data table corresponding to the class data model exists in the database, further comprising:
and when the attribute type of the class data model is consistent with the attribute type of the database, creating an insertion SQL sentence, and executing insertion of the service data.
6. A terminal database data migration system, comprising:
the receiving module is used for receiving the service data issued by the server if the database exists;
the first conversion module is used for converting the service data into a class data model;
the first checking module is used for checking whether a data table corresponding to the class data model exists in the database;
the second checking module is used for further checking whether the attribute type of the class data model is consistent with the attribute type of the database if the data table corresponding to the class data model exists in the database;
the migration module is used for creating a new data table in the database when the attribute type of the class data model is inconsistent with the attribute type of the database, migrating the data of the original data table in the database to the new data table, and deleting the original data table;
the converting the service data into a class data model specifically comprises:
recursively and circularly analyzing the nesting relation of the service data, and establishing a attribution relation queue of a class data model;
circularly taking out an attribute list of the service data from the top of the attribution relation queue, generating a corresponding class data model by utilizing a dynamic runtime reflection mechanism, and further generating class definition and class files, wherein the class names of the classes use packet names of the service data, and the class files are added with fixed prefixes before the class names;
when a corresponding class data model is generated by utilizing a dynamic runtime reflection mechanism, adding the class data model generated in the last cycle as a sub-attribute of the class data model;
creating a new data table in the database when the attribute type of the class data model is inconsistent with the attribute type of the database, migrating the data of the original data table in the database to the new data table, and deleting the original data table specifically comprises:
when the attribute type of the class data model is inconsistent with the attribute type of the database, converting the attribute type of the class data model into the attribute type of the database, and creating a new data table in the database;
starting an asynchronous sub-thread and a database transaction, and migrating the data of an original data table in the database to the new data table;
and deleting the original data table in the database, and ending the asynchronous sub-thread and the database transaction.
7. The terminal database data migration system of claim 6, wherein said system further comprises:
the first creating module is used for creating the database and receiving the service data issued by the server if the database does not exist.
8. The terminal database data migration system of claim 6, wherein said system further comprises:
and the insertion module is used for creating an SQL sentence when the attribute type of the class data model is consistent with the attribute type of the database, and executing the insertion of the service data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811571916.7A CN111352918B (en) | 2018-12-21 | 2018-12-21 | Terminal database data migration method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811571916.7A CN111352918B (en) | 2018-12-21 | 2018-12-21 | Terminal database data migration method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111352918A CN111352918A (en) | 2020-06-30 |
| CN111352918B true CN111352918B (en) | 2023-05-23 |
Family
ID=71197107
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811571916.7A Active CN111352918B (en) | 2018-12-21 | 2018-12-21 | Terminal database data migration method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111352918B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101339559A (en) * | 2008-07-18 | 2009-01-07 | 北京航空航天大学 | Long lasting implementing method for data |
| CN101739436A (en) * | 2009-09-28 | 2010-06-16 | 孙彬 | XML-based flexible data migration method |
| CN102508929A (en) * | 2011-12-01 | 2012-06-20 | 浪潮(北京)电子信息产业有限公司 | System, device and method for realizing data migration of heterogeneous database |
| CN102968306A (en) * | 2012-11-29 | 2013-03-13 | 广东全通教育股份有限公司 | Method and system for automatically generating code based on data model drive |
| CN103176988A (en) * | 2011-12-21 | 2013-06-26 | 上海博腾信息科技有限公司 | Data migration system based on software-as-a-service (SaaS) |
| CN103440285A (en) * | 2013-08-14 | 2013-12-11 | 北京乐动卓越科技有限公司 | Large-scale mobile phone game system and database updating method of large-scale mobile phone game system |
| CN105373599A (en) * | 2015-10-28 | 2016-03-02 | 北京汇商融通信息技术有限公司 | Data migration system based on various data storage platforms |
| CN106126543A (en) * | 2016-06-15 | 2016-11-16 | 清华大学 | A kind of relevant database is to the model conversion of MongoDB and data migration method |
| CN106649771A (en) * | 2016-12-27 | 2017-05-10 | 广州杰赛科技股份有限公司 | Data model updating method and system for database |
| CN107958057A (en) * | 2017-11-29 | 2018-04-24 | 苏宁云商集团股份有限公司 | A kind of code generating method and device for being used for Data Migration in heterogeneous database |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040064487A1 (en) * | 2002-10-01 | 2004-04-01 | Nguyen Liem M. | Method and apparatus to migrate a database |
| US7676492B2 (en) * | 2006-04-07 | 2010-03-09 | International Business Machines Corporation | Migration of database using serialized objects |
| US10268633B2 (en) * | 2016-03-29 | 2019-04-23 | Wipro Limited | System and method for database migration with target platform scalability |
-
2018
- 2018-12-21 CN CN201811571916.7A patent/CN111352918B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101339559A (en) * | 2008-07-18 | 2009-01-07 | 北京航空航天大学 | Long lasting implementing method for data |
| CN101739436A (en) * | 2009-09-28 | 2010-06-16 | 孙彬 | XML-based flexible data migration method |
| CN102508929A (en) * | 2011-12-01 | 2012-06-20 | 浪潮(北京)电子信息产业有限公司 | System, device and method for realizing data migration of heterogeneous database |
| CN103176988A (en) * | 2011-12-21 | 2013-06-26 | 上海博腾信息科技有限公司 | Data migration system based on software-as-a-service (SaaS) |
| CN102968306A (en) * | 2012-11-29 | 2013-03-13 | 广东全通教育股份有限公司 | Method and system for automatically generating code based on data model drive |
| CN103440285A (en) * | 2013-08-14 | 2013-12-11 | 北京乐动卓越科技有限公司 | Large-scale mobile phone game system and database updating method of large-scale mobile phone game system |
| CN105373599A (en) * | 2015-10-28 | 2016-03-02 | 北京汇商融通信息技术有限公司 | Data migration system based on various data storage platforms |
| CN106126543A (en) * | 2016-06-15 | 2016-11-16 | 清华大学 | A kind of relevant database is to the model conversion of MongoDB and data migration method |
| CN106649771A (en) * | 2016-12-27 | 2017-05-10 | 广州杰赛科技股份有限公司 | Data model updating method and system for database |
| CN107958057A (en) * | 2017-11-29 | 2018-04-24 | 苏宁云商集团股份有限公司 | A kind of code generating method and device for being used for Data Migration in heterogeneous database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111352918A (en) | 2020-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258989B (en) | Database migration evaluation method and device, storage medium and computer equipment | |
| CN108228817B (en) | Data processing method, device and system | |
| CN109951315B (en) | Method and system for mapping YANG model to internal model | |
| CN109857724B (en) | Method and equipment for supporting various databases based on block chain | |
| US10089371B2 (en) | Extensible extract, transform and load (ETL) framework | |
| CN112217656B (en) | Method and device for synchronizing configuration information of network equipment in SD-WAN (secure digital-to-Wide area network) system | |
| WO2012034440A1 (en) | Method and device for generating database upgrading script | |
| CN111324333B (en) | Software development method and device based on componentization | |
| US9450985B2 (en) | Server validation with dynamic assembly of scripts | |
| CN106302592A (en) | The update method of terminal applies, server and terminal | |
| US6941309B2 (en) | Object integrated management system | |
| CN110941629B (en) | Metadata processing method, apparatus, device and computer readable storage medium | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN113051229A (en) | User data acquisition method, device, terminal and readable storage medium | |
| CN114443015A (en) | Method for generating adding, deleting, modifying and checking service interface based on database metadata | |
| CN111352918B (en) | Terminal database data migration method and system | |
| CN111198678A (en) | Method and device for generating GraphQL front-end operation interface | |
| CN109947739B (en) | Data source management method and device | |
| CN111125129A (en) | Data processing method and device, storage medium and processor | |
| CN114356404A (en) | Interface document generating method, system and computer readable storage medium | |
| CN111858609A (en) | Fuzzy query method and device for block chain | |
| CN106681914B (en) | Television picture quality debugging method and device | |
| CN113535221A (en) | Method and device for managing application version | |
| CN110737506A (en) | virtual machine image version management method | |
| CN116302206B (en) | Presto data source hot loading method based on MQ |
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 | ||
| CB02 | Change of applicant information |
Address after: 518000 w601, Shenzhen Hong Kong industry university research base, 015 Gaoxin South 7th Road, high tech Zone community, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: ASPIRE TECHNOLOGIES (SHENZHEN) LTD. Address before: 518000 south wing, 6th floor, west block, Shenzhen Hong Kong industry university research base building, South District, high tech Industrial Park, Nanshan District, Shenzhen City, Guangdong Province Applicant before: ASPIRE TECHNOLOGIES (SHENZHEN) LTD. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |