CN111352918A - Terminal database data migration method and system - Google Patents
Terminal database data migration method and system Download PDFInfo
- Publication number
- CN111352918A CN111352918A CN201811571916.7A CN201811571916A CN111352918A CN 111352918 A CN111352918 A CN 111352918A CN 201811571916 A CN201811571916 A CN 201811571916A CN 111352918 A CN111352918 A CN 111352918A
- Authority
- CN
- China
- Prior art keywords
- database
- data
- class
- attribute type
- data model
- 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.)
- Granted
Links
- 230000005012 migration Effects 0.000 title claims abstract description 52
- 238000013508 migration Methods 0.000 title claims abstract description 52
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000013499 data model Methods 0.000 claims abstract description 120
- 230000007246 mechanism Effects 0.000 claims description 10
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 abstract description 4
- 230000006872 improvement Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000002035 prolonged effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000008263 repair mechanism Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a terminal database data migration method, which comprises the following steps: if the database exists, receiving the 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 a 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. 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 method and a system for migrating terminal database data, which realize automatic, real-time and silent migration of a terminal database, improve the 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 system.
Background
In the field of software development related to existing terminal clients (IOS/Android), a requirement for database data migration exists, for example, in an iterative development process of a software system, because a new requirement causes a change (addition/deletion) of an attribute of a data table of a client (IOS/Android), a new data table needs to be created, then data of an old data table is migrated into the new data table, and meanwhile, the old data table is deleted and the new data table is modified into a name of an old database.
Aiming at the existing first data migration method, when a new version client (IOS/Android) realizes data migration of a database, the data migration of the database can be triggered only after a user upgrades the client (IOS/Android), and real-time data migration cannot be realized; for the second data migration method in the prior art, when the data migration of the database is implemented by using the hot repair principle, if the hot patch version is too many, the hot patch version management also needs a large performance overhead, and meanwhile, the IOS operating system has prohibited the use of the hot repair mechanism, and the Android operating system also disables a part of the capability of the hot repair principle in the newly released version, which is inconvenient.
Disclosure of Invention
The present invention is directed to solving, at least to some extent, one of the technical problems in the related art. To this end, it is an object of the present invention 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 method for migrating data in a terminal database, including:
if the database exists, receiving the 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 the database has a data table corresponding to the class data model, 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 and receiving the service data sent by the server if the database does not exist.
As a further improvement of the above scheme, the converting the service data into the class data model specifically includes:
recursively and circularly analyzing the nesting relation of the service data, and establishing an attribution relation queue of a class data model;
circularly taking out the 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 definitions and class files, wherein the class names of the classes use the packet names of the service data, and fixed prefixes are added to the class files before the class names;
and when a corresponding class data model is generated by utilizing a dynamic operation reflection mechanism, adding the class data model generated in the previous cycle as the sub-attribute of the class data model.
As a further improvement of the above solution, the checking whether a data table corresponding to the class data model exists in the database specifically includes:
and performing recursive circulation to inquire whether a corresponding data table exists in the database through the class name and 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 database does not have a data table corresponding to the class data model, converting the attribute type of the class data model into the attribute type of the database;
creating a data table SQL statement and executing to create a new data table;
and creating an insert SQL statement and executing insert of the business data.
As a further improvement of the above scheme, 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 database has the data table corresponding to the class data model, 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 insert SQL statement and executing the insert of the business data.
As a further improvement of the foregoing solution, 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 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 asynchronous sub-thread and database transaction, and migrating the data of the 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 a 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 solution, the system further comprises:
and the first creating module is used for creating the database and receiving the service data sent by the server if the database does not exist.
As a further improvement of the above solution, the system further comprises:
and the inserting module is used for creating an inserting SQL statement and executing inserting the business data when the attribute type of the class data model is consistent with the attribute type of the database.
The invention has the beneficial effects that:
the invention relates to a terminal database data migration method and a system, which are used for checking whether a data table corresponding to a class data model exists in a database and checking whether the attribute type of the class data model is consistent with the attribute type of the database when the terminal database exists, so that data migration is carried out, the technical problem that in the prior art, the data migration of the database can be triggered only after a user upgrades a client (IOS/Android) or is forbidden by an official operating system when the data migration of the database is realized through a thermal restoration principle is solved, 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 (IOS/Android) caused by the change of the structure of the data table is reduced, the response time of software requirements is prolonged, and the user experience is improved.
Drawings
The following further describes embodiments of the present invention with reference to the accompanying drawings:
fig. 1 is a schematic flowchart of a terminal database data migration method according to a first embodiment of the present invention;
fig. 2 is a schematic 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 the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Example one
Fig. 1 is a schematic flowchart 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 the service data sent by the server;
s02, converting the service data into a class data model;
s03, checking whether a data table corresponding to the class data model exists in the database;
s04, if the database has a data table corresponding to the class data model, further checking whether the attribute type of the class data model is consistent with the attribute type of the database;
and 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:
and S00, if the database does not exist, creating a database and receiving the service data sent by the server.
In this embodiment, step S02 specifically includes:
s021, recursively and circularly analyzing the nesting relation of the service data, and establishing an attribution relation queue of the class data model;
s022, circularly taking out an attribute list of the service data from the top of the affiliation relation queue, generating a corresponding class data model by using a dynamic runtime reflection mechanism, and further generating class definitions and class files, wherein the class names of the classes use the registration of the service data, and fixed prefixes are added to the class files before the class names;
s023, when the corresponding class data model is generated by utilizing the dynamic runtime reflection mechanism, adding the class data model generated in the previous cycle as the sub-attribute of the class data model.
In this embodiment, step S03 specifically includes:
and recursively circulating the class names and subclasses of the same class data model, and inquiring whether a corresponding data table exists in the database.
In this embodiment, after step S03, the method further includes the steps of:
s06, if the database does not have a data table corresponding to the class data model, converting the attribute type of the class data model into the attribute type of the database;
s07, creating a data table SQL statement 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:
and S09, when the attribute type of the class data model is consistent with the attribute type of the database, creating an insert SQL statement and executing insert 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-half comparison by using a dichotomy;
if the attribute name of the class data model is consistent with the attribute name of the database, converting the attribute type of the class data model into the attribute type of the database, further comparing the attribute class name of the class data model with the attribute class name of the database, and checking whether the attribute class name of the class data model is consistent with the attribute class name of the database.
In this embodiment, step S05 specifically includes:
s051, when the attribute type of the class data model is not consistent 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 asynchronous sub thread and database affairs, and transferring the data of the original data table in the database to a new data table;
and 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 flowchart illustrating 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 the database exists, if not, executing step S2, if yes, executing step S3;
s2, creating a database;
s3, receiving service data sent by the server;
s4, converting the service 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 a step S6, and if so, executing a 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 insert SQL statement, executing insert business data and ending the process;
s9, checking whether the attribute type of the class data model is consistent with the attribute type of the data table, if so, executing a step S8, and if not, executing a step S10;
s10, converting the attribute type of the class data model into the attribute type of the database;
s11, creating a new data table;
s12, starting asynchronous sub thread and database affairs;
s13, migrating the data of the original data table in the database to a new data table;
and 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: the client checks whether the database exists using the package name, and if not, step S2 is executed, and if so, step S3 is executed.
In this embodiment, step S2 specifically includes: creating a database 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 an attribution relation queue of the class data model;
s32, circularly taking out an attribute list of the service data from the top of the affiliation relation queue, generating a corresponding class data model by using a dynamic runtime reflection mechanism, wherein the class data model comprises a class dynamic runtime mechanism, class polymorphism, inheritance and the like, and the class data model attributes are written in a one-to-one correspondence manner by using a reflection means, so as to generate class definitions 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 on the basis of the class names;
and S33, when a corresponding class data model is generated by using a dynamic operation reflection mechanism, adding the class data model generated in the previous cycle as the sub-attribute of the current class data model.
In this embodiment, step S5 specifically includes: the recursion loop checks whether a data table corresponding to the class data model exists in the database through the class name and subclass of the class data model, if not, step S6 is executed, and if so, step S9 is executed.
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;
and S62, establishing a corresponding relation between the class data model attribute and the database attribute, and converting the class data model attribute and the database attribute into the types of the attributes in the data table respectively by using a dynamic runtime reflection mechanism.
In this embodiment, step S7 specifically includes: and the recursion loop creates a data table SQL statement in the database through the class name and subclass of the class data model and executes the creation of a new data table.
In this embodiment, step S9 specifically includes:
s91, comparing the attribute name of the class data model with the attribute name of the database, and performing half-half comparison by using a dichotomy;
s92, if the attribute name of the class data model is consistent with the attribute name of the database, converting the attribute type of the class data model into the attribute type of the database, further comparing the attribute class name of the class data model with the attribute class name of the database, checking whether the attribute class name of the class data model is consistent with the attribute class name of the database, if so, executing the step S8, and if not, executing the step S10.
In this embodiment, step S12 is executed to prepare for data migration.
In this embodiment, step S13 specifically includes:
s131, circulating the number of records of the original data table, and inserting one record of the original data table into the new data table;
and S132, deleting the records 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.
The invention discloses a terminal database data migration method, which is characterized in that when a terminal database exists, whether a data table corresponding to a 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 carried out, the technical problem that in the prior art, the data migration of the database can be triggered only after a user upgrades a client (IOS/Android) or is forbidden by an official operating system when the data migration of the database is realized through a thermal restoration principle is solved, automatic, real-time and silent migration of the terminal database is realized, no any service or scene is needed, 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 prolonged, 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 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 a 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:
and the first creating module is used for creating the database and receiving the service data sent 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 creating module is used for creating the data table SQL statement and executing the creation of a new data table.
In this embodiment, the migration system further includes:
the inserting module is used for creating an inserting SQL statement and executing inserting business data; and the inserting module is also used for creating an inserting SQL statement and executing inserting 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 configured to execute the terminal database data migration method in the first embodiment, and the working principles and beneficial effects thereof are in one-to-one correspondence, and thus are not described again.
The invention relates to a terminal database data migration method and a system, which are used for checking whether a data table corresponding to a class data model exists in a database and checking whether the attribute type of the class data model is consistent with the attribute type of the database when the terminal database exists, so that data migration is carried out, the technical problem that in the prior art, the data migration of the database can be triggered only after a user upgrades a client (IOS/Android) or is forbidden by an official operating system when the data migration of the database is realized through a thermal restoration principle is solved, 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 (IOS/Android) caused by the change of the structure of the data table is reduced, the response time of software requirements is prolonged, and the user experience is improved.
While the preferred embodiments of the present invention have been illustrated and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A terminal database data migration method is characterized by comprising the following steps:
if the database exists, receiving the 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 the database has a data table corresponding to the class data model, 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.
2. The method for migrating database of terminal according to claim 1, further comprising creating a database and receiving the service data from the server if the database does not exist.
3. The method for migrating terminal database data according to claim 1, wherein the converting the service data into the class data model specifically comprises:
recursively and circularly analyzing the nesting relation of the service data, and establishing an attribution relation queue of a class data model;
circularly taking out the 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 definitions and class files, wherein the class names of the classes use the packet names of the service data, and fixed prefixes are added to the class files before the class names;
and when a corresponding class data model is generated by utilizing a dynamic operation reflection mechanism, adding the class data model generated in the previous cycle as the sub-attribute of the class data model.
4. The method for migrating terminal database data according to claim 1, wherein the checking whether the database has the data table specific to the class data model comprises:
and performing recursive circulation to inquire whether a corresponding data table exists in the database through the class name and subclass of the class data model.
5. The method for migrating terminal database data according to claim 4, further comprising, after the step of checking whether the database has the data table corresponding to the class data model:
if the database does not have a data table corresponding to the class data model, converting the attribute type of the class data model into the attribute type of the database;
creating a data table SQL statement and executing to create a new data table;
and creating an insert SQL statement and executing insert of the business data.
6. The method for migrating terminal database data according to claim 1, wherein, if a data table corresponding to the class data model exists in the database, the step of further checking whether the attribute type of the class data model is consistent with the attribute type of the database further comprises:
and when the attribute type of the class data model is consistent with the attribute type of the database, creating an insert SQL statement and executing the insert of the business data.
7. The method according to claim 1, wherein 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 asynchronous sub-thread and database transaction, and migrating the data of the 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.
8. 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 a 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.
9. The system for migrating terminal database data according to claim 8, further comprising:
and the first creating module is used for creating the database and receiving the service data sent by the server if the database does not exist.
10. The system for migrating terminal database data according to claim 8, further comprising:
and the inserting module is used for creating an inserting SQL statement and executing inserting the business data when the attribute type of the class data model is consistent with the attribute type of the database.
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 true CN111352918A (en) | 2020-06-30 |
| CN111352918B 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 (13)
| 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 |
| US20070239774A1 (en) * | 2006-04-07 | 2007-10-11 | Bodily Kevin J | Migration of database using serialized objects |
| CN101339559A (en) * | 2008-07-18 | 2009-01-07 | 北京航空航天大学 | A method for implementing data persistence |
| 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 |
| US20170286412A1 (en) * | 2016-03-29 | 2017-10-05 | Wipro Limited | System and method for database migration with target platform scalability |
| 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 |
-
2018
- 2018-12-21 CN CN201811571916.7A patent/CN111352918B/en active Active
Patent Citations (13)
| 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 |
| US20070239774A1 (en) * | 2006-04-07 | 2007-10-11 | Bodily Kevin J | Migration of database using serialized objects |
| CN101339559A (en) * | 2008-07-18 | 2009-01-07 | 北京航空航天大学 | A method for implementing data persistence |
| 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 |
| US20170286412A1 (en) * | 2016-03-29 | 2017-10-05 | Wipro Limited | System and method for database migration with target platform scalability |
| 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 |
|---|---|
| CN111352918B (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113986873B (en) | Method for processing, storing and sharing data modeling of mass Internet of things | |
| CN110555015B (en) | Database entity management method and device, electronic equipment and storage medium | |
| US9450985B2 (en) | Server validation with dynamic assembly of scripts | |
| CN108932236A (en) | A kind of file management method, scratch file delet method and device | |
| CN106776783B (en) | Unstructured data memory management method and system | |
| US10089371B2 (en) | Extensible extract, transform and load (ETL) framework | |
| CN110941629B (en) | Metadata processing method, apparatus, device and computer readable storage medium | |
| CN111443920B (en) | Frame migration method and device | |
| CN112800010A (en) | HDFS file automatic cleaning method and device and storage medium | |
| CN112217656A (en) | Method and device for synchronizing configuration information of network equipment in SD-WAN (secure digital-to-Wide area network) system | |
| CN116663050A (en) | Intelligent contract data rapid query method based on database | |
| CN110737506A (en) | virtual machine image version management method | |
| CN111381820A (en) | Method and device for automatically generating API based on GUI | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN113792026A (en) | Deployment method and device of database script and computer readable storage medium | |
| CN110795431B (en) | Environment monitoring data processing method, device, equipment and storage medium | |
| CN114546563B (en) | Multi-tenant page access control method and system | |
| CN113495894A (en) | Data synchronization method, device, equipment and storage medium | |
| CN112579877A (en) | Information source system control method, device, storage medium and equipment | |
| CN111352918B (en) | Terminal database data migration method and system | |
| CN112448979B (en) | Cache information updating method, device and medium | |
| CN113535221A (en) | Method and device for managing application version | |
| CN109947739A (en) | Data power supply management method and device | |
| CN115686497A (en) | Business development data management method, development engine, electronic device, and storage medium | |
| CN114356404A (en) | Interface document generating method, system and computer readable storage medium |
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 |