CN112559079A - Data source connection driving self-adaptive loading method and device and electronic equipment - Google Patents
Data source connection driving self-adaptive loading method and device and electronic equipment Download PDFInfo
- Publication number
- CN112559079A CN112559079A CN202011531041.5A CN202011531041A CN112559079A CN 112559079 A CN112559079 A CN 112559079A CN 202011531041 A CN202011531041 A CN 202011531041A CN 112559079 A CN112559079 A CN 112559079A
- Authority
- CN
- China
- Prior art keywords
- data source
- driver
- source connection
- connection
- package
- 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.)
- Withdrawn
Links
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure provides a data source connection driving self-adaptive loading method and device and electronic equipment, which are used for solving the technical problem that data integration software cannot be accessed to a target data source in a self-adaptive manner. According to the technical scheme, the data source connection driving program is packaged in the driving program package, the data source connection objects of corresponding versions are sequentially constructed through the self-defined loading tool according to the driving list in the driving program package, and when the constructed data source connection objects are successfully connected with the target data source, the version adaptation is successful. By the method, the self-adaptive adaptation of the big data integration software to the data source connection driving version of the target database is realized, so that the big data integration software is more friendly to users, and the data connection is more flexible and intelligent.
Description
Technical Field
The disclosure relates to the technical field of big data, in particular to a data source connection driving self-adaptive loading method and device and electronic equipment.
Background
In the field of big data technology, data integration technology is responsible for converting data in a plurality of scattered data sources and integrating the data into a unified data set to solve the phenomenon of information isolated island in information system construction, provide comprehensive data sharing for enterprises and create value for production of life.
The data integration refers to that a product supports various data sources, can be in butt joint with the various data sources to provide data synchronization, conversion and migration capabilities, and is an essential link in big data analysis and processing. Data integration technology is widely paid attention increasingly, one technology playing an important role in data integration is data access, a data integration system faces a large number of heterogeneous data sources, common relational databases such as SQLServer, Oracle, Postgrs and the like and data source types such as hive and hbase in big data Hadoop ecology already or gradually support data source connection interface types such as Java data source connection (Java JDBC) driver, Open data source connection (ODBC) driver and the like, and data interaction with the databases through the data source connection driver is a very important data interaction means.
After the data integration product is released online, assuming that a database version used by a field client a is Oracle18c, a version of a data source connection driver of the database version is also an 18c version, and a database version of another client B may be Oracle 12c, and a version of a data source connection driver of the database version is also a 12c version, if the version of the data source connection driver of the Oracle database built in the data integration product is Oracle 12c, the data integration product cannot support the client a because the low version driver cannot be compatible with the database version upwards, unless the background drive jar package is manually replaced by Oracle18c, and then jvm is restarted, which will certainly interrupt the existing service of the client B. If the JDBC driver of a database is downward compatible, perhaps by issuing a live version upgrade of the data integration system with a new driver (e.g., Oracle18 c), then another scenario is not sufficient, e.g., the customer site Mysql database version is 8, however, the premade Mysql5 of the data integration system supports versions 5 and below, and since Mysql itself has a version jump in the database, if the Mysql8 version is supported by upgrading the Mysql drive, the previous 5 versions cannot be supported, which is not customer friendly, in the traditional non-containerized form, a jar packet may be manually replaced on site and then restarted, so that the registered access of the data source is reluctantly completed, however, this causes service interruption and requires manual replacement of jar packets of JDBC, which results in poor product flexibility and usability.
Disclosure of Invention
In view of this, the present disclosure provides a data source connection driving adaptive loading method and apparatus, and an electronic device, which are used to solve the technical problem that data integration software cannot adaptively access a target data source.
Based on a flow chart of steps of a data source connection driving adaptive loading method provided by an embodiment of the present disclosure as shown in fig. 1, the method includes:
acquiring data source connection driving programs of different versions of a specified data source type, and packaging the acquired data source connection driving programs of different versions to generate a driving program package;
establishing a data source connection driver list comprising a driver main class name and a driver storage path based on the data source connection driver version included in the driver package;
when connecting the target data source of the specified data source type, trying to load the data source connection driver versions corresponding to the records one by one based on the records in the data source connection driver list, connecting the target data source, terminating the try when the connection is successfully established, and returning the session connection of the target data source.
Based on the embodiment of the present disclosure, further, the method for acquiring data source connection drivers of different versions of a specified data source type and packaging the acquired data source connection drivers of different versions to generate a driver package includes:
and connecting the data sources of multiple versions with the driver in a pre-built-in mode and packaging to generate the driver package.
Based on the embodiment of the present disclosure, further, when a new data source connection driver version needs to be supported, the method for acquiring the data source connection drivers of different versions of the specified data source type and packaging the acquired data source connection drivers of different versions to generate the driver package includes:
and acquiring a new version of the data source connection driver through a data source drive management page of the data integration management system, and packaging the new version of the data source connection driver into a pre-built driver package.
Based on the embodiment of the present disclosure, further, the method for generating the driver package by packaging includes:
packaging the obtained driver package into a data integration software installation package through a general compiling integration tool, and comprising the following steps:
decompressing a temporary software package of the data integration software installation package to a specified directory by using a general compiling and integrating tool;
placing the acquired data source connection driving program with different versions into the subdirectory of the specified directory
And compressing and compiling the designated directory into a data integration software installation package comprising the driver package by using a general compiling and integrating tool.
Based on the embodiment of the disclosure, further, a record is sequentially taken out from the data source connection driver list, and a corresponding data source connection object is instantiated by using a self-defined class loading tool class by taking the main class name and the driver storage path of the data source connection driver in the record as parameters;
and the data source connection object initializes and establishes connection with the target data source, if the connection establishment fails, other records are continuously tried in sequence, and if the connection establishment succeeds, the attempt is terminated and the session connection of the target data source is returned.
Based on the schematic diagram of the logical structure of the data source connection driving adaptive loading device provided by the embodiment of the present disclosure shown in fig. 2, each functional module in the device may be implemented in the form of a software module, or implemented in the form of a hardware unit. The apparatus 200 comprises:
the multi-version driver packaging module 201 is configured to acquire data source connection drivers of different versions of a specified data source type, and package the acquired data source connection drivers of different versions to generate a driver package;
the driver list establishing module 202 is configured to establish a data source connection driver list including a driver main class name and a driver storage path based on the data source connection driver version included in the driver package;
the adaptive driver loading module 203 is configured to, when a target data source of the specified data source type is connected, attempt to load a data source connection driver version corresponding to a record one by one based on the record in the data source connection driver list, connect to the target data source, terminate the attempt when the connection is successfully established, and return to a session connection of the target data source.
Based on the embodiment of the present disclosure, further, the multi-version driver packaging module 201 connects multiple versions of data sources to a driver in a pre-built-in manner to package the data sources into a driver package.
Based on the embodiment of the present disclosure, further, the multi-version driver packaging module 201 obtains a new version of the data source connection driver through the data source driver management page of the data integration management system, and packages the new version of the data source connection driver into a driver package that is built in advance.
Based on the embodiment of the present disclosure, further, the adaptive driver loading module 203 sequentially takes out a record from the data source connection driver list, uses the main class name and the driver storage path of the data source connection driver in the record as parameters, and instantiates a corresponding data source connection object using the self-defined class loading tool class; initializing a data source connection object and establishing a connection with a target data source, continuously and sequentially trying other records if the connection is failed to be established, and terminating the trial and returning the session connection of the target data source if the connection is successfully established.
Based on the schematic structural diagram of an electronic device provided in an embodiment of the present disclosure as shown in fig. 3, the device 300 includes: a processor 310, such as a Central Processing Unit (CPU), an internal bus 320, a network interface 340, and a computer-readable storage medium 330. Wherein the processor 310 and the computer-readable storage medium 330 can communicate with each other through the internal bus 320. The computer-readable storage medium 330 may store therein a computer program provided by the present disclosure for implementing the above-mentioned data source connection-driven adaptive loading method, and when the computer program is executed by the processor 310, the functions of the steps of the method provided by the present disclosure can be implemented. The machine-readable storage medium may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Additionally, the machine-readable storage medium may be at least one memory device located remotely from the aforementioned processor. The Processor may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), etc.; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
According to the technical scheme, the data source connection driving program is packaged in the driving program package, the data source connection objects of corresponding versions are sequentially constructed through the self-defined loading tool according to the driving list in the driving program package, and when the constructed data source connection objects are successfully connected with the target data source, the version adaptation is successful. By the method, the self-adaptive adaptation of the big data integration software to the data source connection driving version of the target database is realized, so that the big data integration software is more friendly to users, and the data connection is more flexible and intelligent.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present disclosure or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present disclosure.
Fig. 1 is a flowchart illustrating steps of a data source connection-driven adaptive loading method according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a logic structure of a data source connection-driven adaptive loading apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
The terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the present disclosure. As used in the embodiments of the present disclosure, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "and/or" as used in this disclosure is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information in the embodiments of the present disclosure, such information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, depending on the context, without departing from the scope of embodiments of the disclosure, and further, the use of the word "if" may be interpreted as "at … …" or "at … …" or "in response to a determination.
The invention provides a scheme which can be applied in the field of data integration and can self-adaptively load data source connection driving programs with different versions, so that the dynamic self-adaptive loading of the data source connection driving programs with different versions of the same or multiple data source types is realized, and the versions of the data source connection driving programs of the database on the client site are self-adaptively matched under the condition of no mutual influence.
The present disclosure is mainly directed to a scenario that a data source connection driver version on a data source side often needs to be matched in data synchronization, migration, and other services in data integration, and more data extraction-Transform-Load (ETL) tools such as a keylet are used in an existing data integration system to support JDBC-driven adaptive dynamic loading.
Fig. 1 is a flowchart illustrating steps of a data source connection-driven adaptive loading method according to an embodiment of the present disclosure, where the data source connection-driven adaptive loading method mainly includes the following four steps:
in order to adaptively connect data sources of different types and versions, a data source connection driver of a corresponding version of a corresponding database needs to be obtained first. In order to better support database connection of different data source types, the method and the device can acquire the main-stream commonly-used driver versions of the data sources, and can load the new driver versions into the driver package through the updating interface after the new driver versions are released. The present disclosure does not limit the type of data source, and may be Hive, Oracle, Phoenix, Mysql, etc. The data source connection driver may be JDBC, ODBC, etc., and the disclosure is not limited thereto, and the JDBC data source connection driver is described as an example below.
In order to implement adaptive loading and avoid a system that interrupts a service when replacing a data source connection driver, the present disclosure provides two possible schemes for acquiring and generating a data source connection driver package (using JDBC as an example):
the first mode is a page uploading mode, an interface capable of uploading different versions of JDBC driver files can be provided through a data source drive management page of the data integrated management system, for example, when a new version data source needs to be connected, the new version of JDBC driver files are uploaded through the interface, and thus a JDBC driver package including multiple versions is generated through a server. For a system with higher security requirement, the security can be improved by performing signature verification on the uploaded driver files. This approach may be supplemented by a preset approach in which, when a new drive version is available, the new version of the drive is packaged into a preset data source connection driver package.
The second mode is a built-in drive mode, that is, the data integration management system is built in all the data source connection drivers of multiple versions which may be used in advance, and generates a JDBC driver package including multiple versions through the server in advance.
The present disclosure requires the use of a universal compilation integration tool to package and generate a data integration software installation package including a data source connection driver package, wherein the universal compilation integration tool (abbreviated as plug-in) may be Maven, Ant, grace, etc., and the plug-in can compile the data source driver into classes and manage program dependent packages, and the universal compilation integration tool supports the execution of user-defined shell scripts during the compilation process. Some basic operations such as copying, decompressing, compressing, etc. can be customized in the shell script. Therefore, the purpose of presetting a plurality of versions of data source connection drivers in the final data integration software installation package is achieved. The work realized by the shell script in the scheme is as follows:
1) and decompressing temporary software packages (including the data integration software program main body and other dependent various jar packages, and not including all required data source connection driving packages at the moment) generated in the plug-in compiling process to a specified directory.
2) And copying the prepared data source connection drivers of different required versions to the appointed subdirectory in a batch mode (for example, the appointed subdirectory A is a path for storing the data source connection drivers, and the general directory A can be in the form of "/lib/data source 3 type/data source connection driver version").
3) And finally, compressing and compiling the designated directory into a final data integration software installation package, namely the software installation package containing various drive versions.
Through the script steps, various drive versions of various data sources are preset in the final data integration software installation package, and preparation is made for dynamic loading of the following drives.
102, establishing a data source connection driving program list comprising a driving program main class name and a driving storage path based on the data source connection driving program version included by the driving program package;
after the driver package is prepared, a driver list is further required to be established, and the data integration software main program can know which data sources in the driver package are connected with the driver version, the driver main class name of each version and the driver storage address through the driver list. For example, the main class name for a data source connection driver for such a scenario as mysql5 is: com, mysql, jdbc, driver, and the names of the main classes driven by the data source connections above mysql5 are: com, mysql, JDBC, cj, driver, in the case of different types of names, the corresponding relationship between the main class name and the driver version needs to be established in a list or array manner, i.e., the main program of the data integration software needs to know what the main class name of the driver corresponding to each JDBC driver version corresponds to, where the driver storage path is.
Examples of possible field formats for records in the data source connection driver list are as follows:
[
“com.mysql.JDBC.Driver:/lib/mysql/5”,
“com.mysql.cj.JDBC.Driver:/lib/mysql/8”，
…
]
wherein, the colon is the main class name before, and the colon is the storage position of the driver after. When the driver list is read into the memory, the driver list can be organized in the forms of a structure array, a linked list and the like, and is not disclosed or limited.
And 103, when the target data source of the specified data source type is connected, trying to load the data source connection driver versions corresponding to the records one by one based on the records in the data source connection driver list, connecting the target data source, terminating the try when the connection is successfully established, and returning the session connection of the target data source.
The step is a key step for realizing the adaptive loading of the data source connection driver, and by taking the JDBC driver as an example, adaptive loading needs to rely on a java self-defined class loading mechanism to realize the coexistence of a plurality of JDBC version drivers.
In an embodiment of the present disclosure, attempting to load a driver in a record one by one based on a record in the data source connection driver list, and a method for connecting a corresponding data source includes:
a record is sequentially taken out from a data source connection driver list, and a corresponding data source connection object is instantiated by using a self-defined class loading tool class by taking a main class name and a drive storage path of a data source connection driver in the record as parameters;
b, initializing a data source connection object and establishing connection with a target data source, executing the step e if the connection is failed to be established, and executing the step f if the connection is successfully established;
if the connection establishment fails, the driver version in the current record is not matched with the database version of the target data source, and if the connection establishment succeeds, the driver version in the current record is successfully matched with the database version of the target data source, and subsequent data transmission can be carried out.
Step e, judging whether all records in the data source driver program list are traversed or not, and if so, terminating the circulation; if not, executing the step a;
and f, returning the session connection of the target data source.
In the above step, a driver in the list is repeatedly tried to be loaded based on the data source connection driver list, where URLClassLoader is a custom class loading tool defined in JDK and responsible for class loading, in an embodiment of the present disclosure, a jar package of data source connection drivers of different versions is loaded using the custom class loading tool, and different urlclassloaders need to correspond to different driver paths.
In a data integration scenario, a situation that a client side has multiple possible data source connection driver versions is often encountered, for example, multiple JDBC versions, and if a platform cannot be compatible with the multiple versions at the same time, a jar packet needs to be manually replaced and then a service system needs to be restarted to realize single support of the driver. According to the technical scheme, the data source connection driver is packaged in the driver package, and the driver version matched with the target data source is adaptively loaded through the self-defined loading tool, so that the data source connection driver version of the target database basically does not need to be concerned. If the target data source is changed with a new version of the data source driver and is not within the preset driver version range of the system, the new driver version can be uploaded by providing a data source drive management interface of the data integration management system, the data source connection driver package is regenerated, and then the adaptive loading cycle is executed again for trial, so that the new data source connection driver version is supported.
It should be recognized that embodiments of the present disclosure can be realized and implemented by computer hardware, a combination of hardware and software, or by computer instructions stored in a non-transitory computer readable memory. The method may be implemented in a computer program using standard programming techniques, including a non-transitory computer readable storage medium configured with the computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner. Each program may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language. Furthermore, the program can be run on a programmed application specific integrated circuit for this purpose.
Further, operations of processes described by the present disclosure may be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The processes described in this disclosure (or variations and/or combinations thereof) may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. The computer program includes a plurality of instructions executable by one or more processors.
Further, the method may be implemented in any type of computing platform operatively connected to a suitable interface, including but not limited to a personal computer, mini computer, mainframe, workstation, networked or distributed computing environment, separate or integrated computer platform, or in communication with a charged particle tool or other imaging device, and the like. Aspects of the disclosure may be embodied in machine-readable code stored on a non-transitory storage medium or device, whether removable or integrated into a computing platform, such as a hard disk, optically read and/or write storage medium, RAM, ROM, or the like, such that it may be read by a programmable computer, which when read by the storage medium or device, is operative to configure and operate the computer to perform the procedures described herein. Further, the machine-readable code, or portions thereof, may be transmitted over a wired or wireless network. The invention described in this disclosure includes these and other different types of non-transitory computer-readable storage media when such media include instructions or programs that implement the steps described above in conjunction with a microprocessor or other data processor. The disclosure also includes the computer itself when programmed according to the methods and techniques described in this disclosure.
The equipment provided by the embodiment of the disclosure and the method provided by the embodiment of the disclosure have the same technical concept and the same beneficial effects as the method adopted, operated or realized by the equipment.
The above description is only an example of the present disclosure and is not intended to limit the present disclosure. Various modifications and variations of this disclosure will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (10)
1. A data source connection driven adaptive loading method is characterized by comprising the following steps:
acquiring data source connection driving programs of different versions of a specified data source type, and packaging the acquired data source connection driving programs of different versions to generate a driving program package;
establishing a data source connection driver list comprising a driver main class name and a driver storage path based on the data source connection driver version included in the driver package;
when connecting the target data source of the specified data source type, trying to load the data source connection driver versions corresponding to the records one by one based on the records in the data source connection driver list, connecting the target data source, terminating the try when the connection is successfully established, and returning the session connection of the target data source.
2. The method of claim 1, wherein the method of obtaining different versions of data source connection drivers of the specified data source type and packaging the obtained different versions of data source connection drivers to generate the driver package comprises:
and connecting the data sources of multiple versions with the driver in a pre-built-in mode and packaging to generate the driver package.
3. The method of claim 2, wherein when a new data source connection driver version needs to be supported, the method of obtaining different versions of data source connection drivers of a specific data source type and packaging the obtained different versions of data source connection drivers to generate a driver package comprises:
and acquiring a new version of the data source connection driver through a data source drive management page of the data integration management system, and packaging the new version of the data source connection driver into a pre-built driver package.
4. The method of claim 2 or 3, wherein the method for generating the driver package by packaging is as follows:
packaging the obtained driver package into a data integration software installation package through a general compiling integration tool, and comprising the following steps:
decompressing a temporary software package of the data integration software installation package to a specified directory by using a general compiling and integrating tool;
placing the acquired data source connection driving program with different versions into the subdirectory of the specified directory
And compressing and compiling the designated directory into a data integration software installation package comprising the driver package by using a general compiling and integrating tool.
5. The method of claim 4,
sequentially taking a record from the data source connection driver list, and instantiating a corresponding data source connection object by using a self-defined class loading tool class by taking a main class name and a drive storage path of the data source connection driver in the record as parameters;
and the data source connection object initializes and establishes connection with the target data source, if the connection establishment fails, other records are continuously tried in sequence, and if the connection establishment succeeds, the attempt is terminated and the session connection of the target data source is returned.
6. A data source connection driven adaptive loading apparatus, comprising:
the multi-version drive packaging module is used for acquiring data source connection driving programs of different versions of the specified data source type and packaging the acquired data source connection driving programs of different versions to generate a driving program package;
the drive list establishing module is used for establishing a data source connection drive program list comprising a drive program main class name and a drive storage path based on the data source connection drive program version included in the drive program package;
and the self-adaptive drive loading module is used for trying to load the data source connection driver versions corresponding to the records one by one based on the records in the data source connection driver list when the target data source of the specified data source type is connected, connecting the target data source, terminating the try when the connection is successfully established, and returning the session connection of the target data source.
7. The apparatus of claim 6,
the multi-version drive packaging module is used for connecting the data sources of the multiple versions with the driver program in a pre-built-in mode and packaging the data sources to generate the driver program package.
8. The apparatus of claim 7,
the multi-version drive packaging module acquires the data source connection driving program of the new version through the data source drive management page of the data integration management system and packages the data source connection driving program of the new version into a driving program package which is built in advance.
9. The apparatus of claim 8,
the self-adaptive drive loading module sequentially takes out a record from the data source connection driver program list, uses the main class name and the drive storage path of the data source connection driver in the record as parameters, and uses a self-defined class loading tool class to instantiate a corresponding data source connection object; initializing a data source connection object and establishing a connection with a target data source, continuously and sequentially trying other records if the connection is failed to be established, and terminating the trial and returning the session connection of the target data source if the connection is successfully established.
10. An electronic device, comprising a processor, a network interface, a machine-readable storage medium and an internal bus, wherein the processor, the network interface and the storage medium communicate with each other via the internal bus;
a machine readable storage medium for storing a computer program;
a processor for implementing the method steps of any of the preceding claims 1-5 when executing a program stored on a machine-readable storage medium.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011531041.5A CN112559079A (en) | 2020-12-22 | 2020-12-22 | Data source connection driving self-adaptive loading method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011531041.5A CN112559079A (en) | 2020-12-22 | 2020-12-22 | Data source connection driving self-adaptive loading method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112559079A true CN112559079A (en) | 2021-03-26 |
Family
ID=75031427
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011531041.5A Withdrawn CN112559079A (en) | 2020-12-22 | 2020-12-22 | Data source connection driving self-adaptive loading method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559079A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113704337A (en) * | 2021-08-26 | 2021-11-26 | 上海德拓信息技术股份有限公司 | Metadata acquisition method and system based on dynamic loading of driver |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1997022925A1 (en) * | 1995-12-15 | 1997-06-26 | Object Dynamics Corp. | Method and system for constructing software components and systems as assemblies of independent parts |
| CN109033436A (en) * | 2018-08-14 | 2018-12-18 | 武汉达梦数据库有限公司 | A kind of multiple version JDBC driving coexistence methods of same database and system |
| CN109558121A (en) * | 2018-11-26 | 2019-04-02 | 上海达梦数据库有限公司 | Development approach, device, equipment and the storage medium of interface drive program |
| CN109857468A (en) * | 2019-01-04 | 2019-06-07 | 烽火通信科技股份有限公司 | A kind of method and system for supporting more DTB in single linux system mirror image |
| CN111679871A (en) * | 2020-08-11 | 2020-09-18 | 上海冰鉴信息科技有限公司 | Database driver loading method and database driver loading device |
-
2020
- 2020-12-22 CN CN202011531041.5A patent/CN112559079A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1997022925A1 (en) * | 1995-12-15 | 1997-06-26 | Object Dynamics Corp. | Method and system for constructing software components and systems as assemblies of independent parts |
| CN109033436A (en) * | 2018-08-14 | 2018-12-18 | 武汉达梦数据库有限公司 | A kind of multiple version JDBC driving coexistence methods of same database and system |
| CN109558121A (en) * | 2018-11-26 | 2019-04-02 | 上海达梦数据库有限公司 | Development approach, device, equipment and the storage medium of interface drive program |
| CN109857468A (en) * | 2019-01-04 | 2019-06-07 | 烽火通信科技股份有限公司 | A kind of method and system for supporting more DTB in single linux system mirror image |
| CN111679871A (en) * | 2020-08-11 | 2020-09-18 | 上海冰鉴信息科技有限公司 | Database driver loading method and database driver loading device |
Non-Patent Citations (1)
| Title |
|---|
| 陈佳等: "面向服务端私有Web API的自动发现技术研究", 《网络与信息安全学报》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113704337A (en) * | 2021-08-26 | 2021-11-26 | 上海德拓信息技术股份有限公司 | Metadata acquisition method and system based on dynamic loading of driver |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10606565B2 (en) | Visual devops systems and methods | |
| US11599348B2 (en) | Container image building using shared resources | |
| US8978023B2 (en) | Canonical mechanism for securely assembling features into a mobile application | |
| CN104793946B (en) | Dispositions method and system are applied based on cloud computing platform | |
| US8332845B2 (en) | Compile timing based on execution frequency of a procedure | |
| US8521359B1 (en) | Application-independent and component-isolated system and system of systems framework | |
| US8862756B2 (en) | Apparatus, system, and method for facilitating data flow between a first application programming interface and a second application programming interface | |
| CN105378689B (en) | Method and apparatus for unified Extensible Firmware Interface (UEFI) driver and agreement | |
| WO2022016848A1 (en) | Method and apparatus for performing application deployment according to service role | |
| Rutherford et al. | Reconfiguration in the Enterprise JavaBean component model | |
| US20120159447A1 (en) | Hardware security module and debugging method of such a module | |
| WO2022148390A1 (en) | Methods for deploying, updating and calling smart contract in blockchain | |
| CN113407362A (en) | SOMEIP communication intermediate layer implementation method and system based on SOA architecture of vehicle-mounted Android system | |
| CN107977260B (en) | Task submitting method and device | |
| CN114756290B (en) | Operating system installation method, device and readable storage medium | |
| CN112559079A (en) | Data source connection driving self-adaptive loading method and device and electronic equipment | |
| JP2013518733A (en) | Robot system control method and apparatus | |
| WO2015062494A1 (en) | Method and device for sdk uploading and downloading of a file | |
| US10310876B2 (en) | Executing application code based on manner of accessing a hard disk | |
| CN116048533B (en) | Implementation method and system for achieving dependency isolation in Flink task running | |
| CN108694048B (en) | Method for realizing batch publishing service | |
| CN114327383A (en) | Service configuration system and method based on SOA (service oriented architecture) middleware and readable storage medium | |
| CN112650512A (en) | Hardware driving method and device, terminal and storage medium | |
| CN111913720A (en) | Program deployment method and device | |
| US10853040B2 (en) | Address space splitting for legacy application compatibility |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210326 |