CN113157784B - Plug-in implementation method of database data export tool - Google Patents
Plug-in implementation method of database data export tool Download PDFInfo
- Publication number
- CN113157784B CN113157784B CN202011608126.9A CN202011608126A CN113157784B CN 113157784 B CN113157784 B CN 113157784B CN 202011608126 A CN202011608126 A CN 202011608126A CN 113157784 B CN113157784 B CN 113157784B
- Authority
- CN
- China
- Prior art keywords
- plug
- template
- driver
- database
- drive
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000011161 development Methods 0.000 claims description 17
- 238000005516 engineering process Methods 0.000 claims description 4
- 238000009795 derivation Methods 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a plug-in implementation method of a database data export tool, belonging to the field of computer software databases; the method comprises the following specific steps: s1, maintaining a driver plug-in of a database by using a drive management system, and providing plug-in uploading, updating and downloading services; s2, maintaining and exporting the template plug-in by using a template management system, and providing services of uploading, updating and downloading the plug-in; s3, a terminal export tool is used for loading a driving plug-in and a template plug-in to export the data of the database; by applying the method, a database export tool with the characteristics of high efficiency, low cost and light weight can be realized, meanwhile, the tool can meet the data export requirement of a multi-source database, has the characteristics of high compatibility and flexible configuration, and avoids the complicated steps when the multi-source database is exported.
Description
Technical Field
The invention discloses a plug-in implementation method of a database data export tool, and relates to the technical field of computer software databases.
Background
In the field of database application development and daily operation and maintenance, data export is a problem often faced by development and operation and maintenance personnel when data migration and data analysis are carried out. With the rise of big data technology, the data volume in the application is greatly increased, and how to effectively export the data of different source databases becomes a problem to be solved urgently in the field of databases. Existing export tools, such as Dumpling, optimized for some characteristics of TiDB, currently support MySQL protocol databases, but do not support exporting multiple database sources; mydumper is a multi-threaded backup recovery tool for MySQL and Drizzle; the same type of export tool also has pg _ dump, which can extract PostgreSQL databases into script files or other archive files; and for example, the export tool aiming at Oracle can only realize data export of Oracle. Most of the common export tools are integrated in a management system of a certain database, and the export operation of the certain database is customized and designed, so that different source databases cannot be simultaneously supported. The invention provides a plug-in implementation method of a database data export tool, which can greatly improve the efficiency of database development and daily maintenance work.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a plug-in implementation method of a database data export tool, which adopts the following technical scheme: a plug-in implementation method of a database data export tool comprises the following specific steps:
s1, maintaining a driver plug-in of a database by using a drive management system, and providing plug-in uploading, updating and downloading services;
s2, a template management system is used for maintaining and exporting the template plug-ins and providing services of uploading, updating and downloading the plug-ins;
and S3, the data of the database is exported by using a terminal export tool to load the driving plug-in and the template plug-in.
The method comprises the following steps that S1, a drive management system is utilized to maintain a driver plug-in connected with a database of which data is required to be exported, and upload, update and download plug-in services are provided, wherein the method specifically comprises the following steps:
s101, storing the drive plug-in provided by the drive management system in a localized mode;
s102, the development drive plug-in is connected to a unified interface of the export tool drive;
s103, obtaining the storage address of the drive according to the url _ header, and downloading the drive plug-in.
The specific steps of the S101 storing the driver plug-in provided by the driver management system in a localized manner are as follows:
s1011, establishing a driver data table by using a local database where the drive management system is located;
s1012, the driver primary key uses the database to connect with the protocol header url _ header to retrieve and update the driver plug-in memory location driver _ address.
S2, the template management system is utilized to maintain exported template plug-ins developed aiming at different platforms, and the specific steps of providing the services of uploading, updating and downloading the plug-ins are as follows:
s201, storing the template plug-in provided by the drive management system in a localized mode;
s202, the development template plug-in is accessed to a uniform interface of the export template;
s203, the storage address of the template is obtained according to the url _ header, and the template plug-in is downloaded.
The specific steps of S201 storing the template plug-in provided by the drive management system in a localized manner are as follows:
s2011 establishes a template data table by using a local database of the template management system;
the S2012template primary key uses the database connection protocol header url _ header to retrieve and update the driver plugin storage location template _ address.
And S3, the corresponding driving plug-ins and template plug-ins of different database sources are loaded by using a terminal export tool to export the data of the database, and the method specifically comprises the following steps:
s301 defines a Driver interface, a Driver factory interface, a Template interface and a Template factory interface;
s302, storing the driving plug-in a driver directory, and storing the backup template plug-in a template directory;
s303, exporting command parameters, analyzing the input command, and finishing the loading of the corresponding database drive plug-in and template plug-in by the terminal exporting tool;
and S304, the internal executor of the terminal export tool calls a Template instance to complete export work according to the built-in execution flow.
The Driver interface and the Driver factor interface defined in the S301 need to be implemented by a Driver plug-in, and the Template interface and the Template factor interface defined by the Driver interface and the Driver factor interface need to be implemented by a Template plug-in, which includes the following specific steps:
s3011, registering a driver factory implementation class and a template factory implementation class in a driver registry and a template registry of a main program of an export tool by using a plug-in technology;
s3012, storing the drive factory implementation classes by using a variable driverFactories of driverRegistry;
s3013, the stored key value is used as a value obtained by a getHeader method of the drive factory implementation class;
s3022 storing the template factory implementation class by using a variable TemplateRegistry of TemplateRegistry;
s3023, the stored key value is used as the value obtained by the getHeader method of the template factory implementation class.
The specific steps of S303 exporting command parameters, analyzing the input command, and finishing the loading of the corresponding database drive plug-in and template plug-in by the terminal exporting tool are as follows:
s3031, finding out a matched driver factory implementation class by a driver registry of the terminal export tool through a specified protocol header;
s3032 calling a creatDriver method of the driver factory to create a drive instance connected with the database;
s3033 calling a createConnection method of Driver to create a connection example of the database;
s3034template registry finds out the matched template factory implementation class through the specified protocol header;
s3035 calls createTemplate method of TemplateFactory to create an export template of the database.
The invention has the beneficial effects that: the database export tool related in the method of the invention is mainly divided into three parts, including a drive management system, a template management system and a terminal export tool; the drive management system has the main functions of providing drive plug-in uploading and downloading services, providing customized drive plug-in development aiming at a multi-platform database and meeting the requirements of different application scenes; the template management system has the main function of providing different export template plug-ins for export operation so as to support different data export types; the terminal export tool part has the main functions of loading plug-ins and analyzing export command parameters to finish export work;
the driving and backup templates of the database export tool are decoupled from the export tool in a plug-in mode, so that the export tool has the characteristic of light weight;
by applying the method, a database export tool with the characteristics of high efficiency, low cost and light weight can be realized, meanwhile, the tool can meet the data export requirement of a multi-source database, has the characteristics of high compatibility and flexible configuration, and avoids the complicated steps when the multi-source database is exported.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention; FIG. 2 is a terminal-to-tool executor workflow diagram of a method embodiment of the present invention; fig. 3 is a schematic diagram of the driving data flow direction according to the embodiment of the present invention.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The first embodiment is as follows:
a plug-in implementation method for a database data export tool comprises the following specific steps:
s1, maintaining a driver plug-in of a database by using a drive management system, and providing plug-in uploading, updating and downloading services;
s2, a template management system is used for maintaining and exporting the template plug-ins and providing services of uploading, updating and downloading the plug-ins;
s3, a terminal export tool is used for loading a driving plug-in and a template plug-in to export data of the database;
the invention relates to a method for realizing plug-in of a database data export tool, which comprises a drive management system, a template management system and a terminal export tool, wherein the drive management system and the template management system are responsible for unified operation and maintenance management by a first inventor, are independent of the terminal export tool, mainly provide plug-in customized development, and have plug-in iterative development, plug-in uploading and downloading services; when the method is used, firstly, a drive management system is utilized to maintain the drive program plug-in of the database according to S1, and the service of uploading, updating and downloading the plug-in is provided;
then, the template plug-in is maintained and exported according to the S2 template management system, the service of uploading, updating and downloading the plug-in is provided,
further, the S1 maintains a driver plug-in connected to a database from which data needs to be exported by using a driver management system, and provides service for uploading, updating, and downloading the plug-in, including the following steps:
s101, storing the drive plug-in provided by the drive management system in a localized mode;
s102, the development drive plug-in is accessed to a unified interface of the export tool drive;
s103, acquiring a storage address of the driver according to the url _ header, and downloading the driver plug-in;
firstly, storing a drive plug-in provided by a drive management system in a localized mode through a Mysql database according to S101, and completing the development of the drive plug-in by a developer accessing the development drive plug-in to a uniform interface of a export tool drive according to S102 for common users and other development operation and maintenance personnel; the user can acquire the storage address of the drive plug-in according to the url _ header in S103, and the download of the drive plug-in can be completed;
still further, the specific step of S101 storing the driver plug-in provided by the driver management system in a localized manner is as follows:
s1011, establishing a driver data table by using a local database where the drive management system is located;
s1012, connecting the driver primary key with a protocol header url _ header by using a database to retrieve and update a driver _ address of a storage position of the driver plug-in;
the data table driver uses the database connection protocol header url _ header as a table driver main key to retrieve and update the drive plug-in storage position driver _ address, and the drive plug-in storage position driver _ address is put under the driver directory of the export tool, so that the drive plug-in can be loaded when the export tool is used.
The second embodiment:
on the basis of the first embodiment, the step S2 of maintaining the exported template plug-ins developed for different platforms by using the template management system includes the following specific steps:
s201, storing the template plug-in provided by the drive management system in a localized mode;
s202, the development template plug-in is accessed to a uniform interface of the export template;
s203, acquiring a storage address of the template according to the url _ header, and downloading the template plug-in;
firstly, according to S201, the template plug-in provided by a drive management system is stored in a local mode through a Mysql database, then according to S202, the template plug-in provided by the template management system is accessed by developers to develop a unified interface of a leading-out tool template, and the development of the drive plug-in is completed and is used by common users and other development or operation and maintenance personnel; finally, the common user obtains the storage address of the template according to the url _ header according to S203 to complete the downloading of the template plug-in;
the specific steps of S201 storing the template plug-in provided by the drive management system in a localized manner are as follows:
s2011 establishes a template data table by using a local database of the template management system;
s2012, the template main key uses the database to connect with the protocol header url _ header to retrieve and update the template _ address of the drive plug-in storage position;
the data table template takes a database connection protocol header url _ header as a table template main key and is used for retrieving and updating a drive plug-in storage position template _ address; a user can acquire the storage address of the template plug-in according to the url _ header, complete the downloading of the template plug-in and place the template plug-in a template directory of the export tool, so that the template plug-in can be loaded when the export tool is used.
Example three:
on the basis of the first or second embodiment, in step S3, the corresponding driver plug-in and template plug-in of different database sources are loaded by using a terminal export tool to export the data of the database, which includes the following specific steps:
s301 defines a Driver interface, a Driver factory interface, a Template interface and a Template factory interface;
s302, storing the driving plug-in a driver directory, and storing the backup template plug-in a template directory;
s303, exporting command parameters, analyzing the input command, and finishing the loading of the corresponding database drive plug-in and template plug-in by the terminal exporting tool;
s304, the internal executor of the terminal export tool calls a Template instance to complete export work according to the built-in execution flow;
firstly, the terminal export tool defines a Driver interface and a Driver factor interface which need to be realized by a driven plug-in and a Template interface which need to be realized by a Template plug-in according to S301, a common user stores the drive plug-in under a Driver directory of the terminal all-around tool according to S302, stores a backup Template plug-in under a Template directory of the terminal export tool, then exports command parameters according to S303, analyzes an input command, and the terminal export tool completes the loading of the corresponding database drive plug-in and Template plug-in;
the method comprises the steps that a common user exports command parameters according to S303 through terminal input, a terminal exporting tool analyzes commands input by the common user, the terminal exporting tool finishes loading corresponding database driving plug-ins and exporting Template plug-ins, and finally a Template instance is called by an internal actuator of the terminal exporting tool according to a built-in execution flow to finish exporting work;
further, the Driver interface and the Driver factor interface defined in S301 need to be implemented by a Driver plug-in, and the Template interface and the Template factor interface defined in S301 need to be implemented by a Template plug-in, which includes the following specific steps:
s3011, registering a driver factory implementation class and a template factory implementation class in a driver registry and a template registry of a main program of an export tool by using a plug-in technology;
s3012, storing and driving the factory implementation classes by using a variable driverFactories of driverRegistry;
s3013, the stored key value is used as a value obtained by a getHeader method of the drive factory implementation class;
s3022 storing the template factory implementation class by using a variable TemplateRegistry of TemplateRegistry;
s3023, taking the stored key value as a value obtained by the getHeader method of the template factory implementation class;
further, the step S303 of exporting the command parameters, analyzing the input command, and the step S of the terminal exporting tool completing the loading of the corresponding database driver plug-in and template plug-in is as follows:
s3031, finding out a matched driver factory implementation class by a driver registry of the terminal export tool through a specified protocol header;
s3032 calling a creatDriver method of the driver factory to create a drive instance connected with the database;
s3033 calling a createConnection method of Driver to create a connection example of the database;
s3034template registry finds out the matched template factory implementation class through the specified protocol header;
s3035 calls createTemplate method of TemplateFactory to create an export template of the database.
When a user inputs derived parameters through a terminal, the driverRegistry finds out a matched driverFactory implementation class through a specified protocol header, then calls a creatDriver method of the driverFactory, creates a driving instance of a connection database, and then calls a creatConnection method of the Driver to create a connection instance of the database; similarly, the template registry finds out the matched template factor implementation class through the specified protocol header, and creates a derivation template of the database in the createTemplate method of calling the template factor; then, the terminal export tool executor calls a Template instance to complete export work according to a built-in execution flow;
the export tool executor can hold instances of two interfaces of Template and Driver and a configuration object analyzed by a command parser, firstly, the Driver is imported through a browser method of Template to create a Connection object to obtain all modes of a database needing to be exported currently, a mode list is circularly traversed, all data tables and views are obtained through a browser table and browser method running Template, whether metadata is exported or not is judged according to the isneedledteta of configuration, if the mode is true, the metadata is obtained through a browser method of Template, then the file is written through a Wiriter, if the mode is false, the metadata is not required to be written into the file, then the view list and the table list are traversed once, if the needledteta is true, the metadata of the table and the constructeview are obtained through a browser table and browser table running Template, the metadata of the table and the view are not required to be exported, if the metadata of the Template table and the metadata of the metadata is not required to be exported, the metadata of the Template table is not required to be exported; when the table is traversed, the selectallfromstable of Template needs to be run to acquire the data iterator Result to finish data reading, and then the Writer writes the data into the file.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (6)
1. A plug-in implementation method for a database data export tool is characterized by comprising the following specific steps:
s1, maintaining a driver plug-in of a database by using a drive management system, and providing plug-in uploading, updating and downloading services;
s2, a template management system is used for maintaining and exporting the template plug-ins and providing services of uploading, updating and downloading the plug-ins;
s3, exporting the data of the database by using a terminal export tool to load a driving plug-in and a template plug-in, and the method comprises the following specific steps:
s301 defines Driver, driver factory interface, template and Template factory interface, and the concrete steps are as follows:
s3011, registering the driverFactory and the template Factory implementation classes into a driverRegistration and a template Registration of a main program of an export tool by using a plug-in technology;
s3012, storing and driving the factory implementation classes by using a variable driverFactories of driverRegistry;
s3013, the stored key value is used as a value obtained by a getHeader method of the drive factory implementation class;
s3022 storing the template factory implementation class by using a variable TemplateRegistry of TemplateRegistry;
s3023 using the stored key value as a value obtained by the getHeader method of the template factory implementation class;
s302, storing the driving plug-in a driver directory, and storing the backup template plug-in a template directory;
s303, exporting command parameters, analyzing the input command, and finishing the loading of the corresponding database drive plug-in and template plug-in by the terminal exporting tool;
and S304, the internal executor of the terminal export tool calls a Template instance to complete export work according to the built-in execution flow.
2. The method according to claim 1, wherein the S1 uses a driver management system to maintain a driver plug-in connected to a database of data to be exported, and provides services for uploading, updating and downloading the plug-in, and the specific steps are as follows:
s101, storing the drive plug-in provided by the drive management system in a localized mode;
s102, the development drive plug-in is connected to a unified interface of the export tool drive;
s103, obtaining the storage address of the drive according to the url _ header, and downloading the drive plug-in.
3. The method as claimed in claim 2, wherein the step S101 of storing the driver plug-in provided by the driver management system in a localized manner comprises the following steps:
s1011, establishing a driver data table by using a local database where the drive management system is located;
s1012, the driver primary key uses the database to connect with the protocol header url _ header to retrieve and update the driver plug-in memory location driver _ address.
4. The method according to claim 1, wherein the step S2 of maintaining exported template plug-ins developed for different platforms by using the template management system comprises the following specific steps:
s201, storing the template plug-in provided by the drive management system in a localized mode;
s202, the development template plug-in is accessed to a uniform interface of the export template;
s203, the storage address of the template is obtained according to the url _ header, and the template plug-in is downloaded.
5. The method according to claim 4, wherein the step S201 of storing the template plug-in provided by the driver management system in a localized manner comprises the following steps:
s2011 establishes a template data table by using a local database of the template management system;
the S2012template primary key uses the database connection protocol header url _ header to retrieve and update the driver plugin storage location template _ address.
6. The method as claimed in claim 1, wherein the step S303 of deriving command parameters, parsing the input command, and the step of the terminal derivation tool completing the loading of the corresponding database driver plug-in and template plug-in is as follows:
s3031, finding out a matched driver factory implementation class by a driver registry of the terminal export tool through a specified protocol header;
s3032 calling a creatDriver method of the driver factory to create a drive instance connected with the database;
s3033 calling a createConnection method of Driver to create a connection example of the database;
s3034template registry finds out the matched template factory implementation class through the specified protocol header;
s3035 calls createTemplate method of TemplateFactory to create an export template of the database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011608126.9A CN113157784B (en) | 2020-12-30 | 2020-12-30 | Plug-in implementation method of database data export tool |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011608126.9A CN113157784B (en) | 2020-12-30 | 2020-12-30 | Plug-in implementation method of database data export tool |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113157784A CN113157784A (en) | 2021-07-23 |
| CN113157784B true CN113157784B (en) | 2023-02-21 |
Family
ID=76878108
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011608126.9A Active CN113157784B (en) | 2020-12-30 | 2020-12-30 | Plug-in implementation method of database data export tool |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113157784B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101258483A (en) * | 2005-09-09 | 2008-09-03 | 易享信息技术（上海）有限公司 | System and method for exporting, publishing, browsing and installing on-demand applications in a multi-tenant database environment |
| CN102663103A (en) * | 2012-04-13 | 2012-09-12 | 北京工业大学 | Configurable method for automatically generating database and accessing data |
| CN102725748A (en) * | 2010-01-26 | 2012-10-10 | 社会传播公司 | Web browser interface for spatial communication environments |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN110321338A (en) * | 2019-06-29 | 2019-10-11 | 长沙曙通信息科技有限公司 | A kind of general data export import tool |
| CN110362617A (en) * | 2019-06-24 | 2019-10-22 | 北京人大金仓信息技术股份有限公司 | Batch data method and system is quickly exported from database based on more concurrent technologies |
| CN111752931A (en) * | 2020-07-01 | 2020-10-09 | 浪潮云信息技术股份公司 | Intelligent storage table implementation method and system for NEWSQL database management system |
| CN111858727A (en) * | 2020-06-24 | 2020-10-30 | 金财互联数据服务有限公司 | Multi-data-source data export system and method based on template configuration |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100585662C (en) * | 2003-06-20 | 2010-01-27 | 汤姆森普罗梅特里克公司 | System and method for computer based testing using cache and cacheable objects to expand functionality of a test driver application |
| US8463667B2 (en) * | 2008-01-11 | 2013-06-11 | Microsoft Corporation | Exporting and importing business templates |
| IN2013CH04267A (en) * | 2013-09-21 | 2015-10-02 | Vayavya Labs Pvt Ltd | |
| US10365641B2 (en) * | 2017-06-19 | 2019-07-30 | Fisher-Rosemount Systems, Inc. | Synchronization of configuration changes in a process plant |
| CN108345682A (en) * | 2018-03-02 | 2018-07-31 | 弘成科技发展有限公司 | Platform and method are imported and exported based on what multi-tenant can configure |
-
2020
- 2020-12-30 CN CN202011608126.9A patent/CN113157784B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101258483A (en) * | 2005-09-09 | 2008-09-03 | 易享信息技术（上海）有限公司 | System and method for exporting, publishing, browsing and installing on-demand applications in a multi-tenant database environment |
| CN102725748A (en) * | 2010-01-26 | 2012-10-10 | 社会传播公司 | Web browser interface for spatial communication environments |
| CN102663103A (en) * | 2012-04-13 | 2012-09-12 | 北京工业大学 | Configurable method for automatically generating database and accessing data |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN110362617A (en) * | 2019-06-24 | 2019-10-22 | 北京人大金仓信息技术股份有限公司 | Batch data method and system is quickly exported from database based on more concurrent technologies |
| CN110321338A (en) * | 2019-06-29 | 2019-10-11 | 长沙曙通信息科技有限公司 | A kind of general data export import tool |
| CN111858727A (en) * | 2020-06-24 | 2020-10-30 | 金财互联数据服务有限公司 | Multi-data-source data export system and method based on template configuration |
| CN111752931A (en) * | 2020-07-01 | 2020-10-09 | 浪潮云信息技术股份公司 | Intelligent storage table implementation method and system for NEWSQL database management system |
Non-Patent Citations (2)
| Title |
|---|
| GDAL多源空间数据访问中间件;刘昌明，陈荤;《地理空间信息》;20111031;第9卷(第5期);全文 * |
| 数据库的导入导出;孤独之影;《CSDN博客》;20200809;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113157784A (en) | 2021-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7694291B2 (en) | Build optimizer tool for efficient management of software builds for mobile devices | |
| US7930318B2 (en) | Systems and methods for implementing a tenant space in a provider-tenant environment | |
| JP4510345B2 (en) | How to dynamically verify resource compatibility | |
| US7739348B2 (en) | Systems and methods for accessing a shared space in a provider-tenant environment by using middleware | |
| US7680825B2 (en) | Systems and methods for generating tenant-specific properties for use in a provider-tenant environment | |
| US7698284B2 (en) | Systems and methods for deploying a tenant in a provider-tenant environment | |
| US20070162969A1 (en) | Provider-tenant systems, and methods for using the same | |
| US20080162509A1 (en) | Methods for updating a tenant space in a mega-tenancy environment | |
| US20040006549A1 (en) | Micro edition dynamic object-driven database manipulation and mapping system | |
| US7844949B2 (en) | Computer method and apparatus for software configuration management repository interoperation | |
| US8630969B2 (en) | Systems and methods for implementing business rules designed with cloud computing | |
| US10726040B2 (en) | Lossless conversion of database tables between formats | |
| US20070156902A1 (en) | Systems and methods for implementing a tenant space in a provider-tenant environment | |
| US20070156849A1 (en) | Systems and methods for delivering software upgrades in a provider-tenant environment | |
| US20070156848A1 (en) | Software management systems and methods, including use of such systems and methods in a provider-tenant environment | |
| US20080162587A1 (en) | Server synchronization for maintenance activities | |
| CN101727475B (en) | Method, device and system for acquiring database access process | |
| EP1691282A1 (en) | Build optimizer tool for efficient management of software builds for mobile devices | |
| US20070156901A1 (en) | Generation and use of table links in a provider-tenant environment | |
| US20070156699A1 (en) | Systems and methods for generating tenant templates for use in a provider-tenant environment | |
| US20070156714A1 (en) | Systems and methods for analyzing tenant-specific properties for use in a provider-tenant environment | |
| CN103853535A (en) | Method and device for modifying middleware | |
| CN114925084A (en) | Distributed transaction processing method, system, device and readable storage medium | |
| CN114356964A (en) | Data blood margin construction method and device, storage medium and electronic equipment | |
| CN113157784B (en) | Plug-in implementation method of database data export tool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |