CN112948454A - Method, device, middleware and computer readable storage medium for accessing database - Google Patents
Method, device, middleware and computer readable storage medium for accessing database Download PDFInfo
- Publication number
- CN112948454A CN112948454A CN201911172693.1A CN201911172693A CN112948454A CN 112948454 A CN112948454 A CN 112948454A CN 201911172693 A CN201911172693 A CN 201911172693A CN 112948454 A CN112948454 A CN 112948454A
- Authority
- CN
- China
- Prior art keywords
- database
- access request
- middleware
- target access
- matching result
- 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.)
- Pending
Links
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/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- 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/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- 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
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The disclosure provides a method, a device, middleware and a computer readable storage medium for accessing a database, and relates to the technical field of information. The method for accessing the database comprises the following steps: the middleware analyzes a database access request sent by an application and obtains a target access element in the database access request; the middleware utilizes the target access element to match the database change information table to obtain a matching result of the target access element; the database change information table comprises various element change information between the new version database and the old version database, and the element change information comprises elements before change and elements after change; and the middleware routes the database access request to the new version database or the old version database according to the matching result of the target access element. According to the method and the device, the data distribution of the application to different databases can be realized on the premise of not modifying the application, so that the restriction of developing a new version application and a new version database is reduced, and the complexity of developing the new version application and the new version database is reduced.
Description
Technical Field
The present disclosure relates to the field of information technology, and in particular, to a method, an apparatus, middleware, and a computer-readable storage medium for accessing a database.
Background
The gray scale distribution is a data distribution mode with smooth transition in the application and database development process. Specifically, the gray release allows some users to continue using the old version of the application and database, and some users to try out the new version of the application and database. If the trial users do not object to the opinion, all users are gradually migrated to the new version application. Gray scale publishing may include both application and database layers.
For the gray release of the database, the database of all users requests the generated data to be distributed to the database instances of the new and old versions at the same time. When the release or rollback is finished, only one database instance needs to be deleted, and the integrity of the business data in the gray release process can be ensured. At present, the gray level distribution of the database is mainly realized through an application layer.
Disclosure of Invention
One technical problem solved by the present disclosure is how to reduce the complexity of developing new versions of applications and databases.
According to an aspect of an embodiment of the present disclosure, there is provided a method of accessing a database, including: the middleware analyzes a database access request sent by an application and obtains a target access element in the database access request; the middleware utilizes the target access element to match the database change information table to obtain a matching result of the target access element; the database change information table comprises various element change information between the new version database and the old version database, and the element change information comprises elements before change and elements after change; and the middleware routes the database access request to the new version database or the old version database according to the matching result of the target access element.
In some embodiments, the matching result of the target access element is element change information corresponding to the target access element; the middleware routing the database access request to the new version database or the old version database according to the matching result of the target access element comprises: the middleware copies the database access request to obtain an original database access request and a copied database access request; if the target access element is an element before the change in the matching result, the middleware modifies the target access element in the copied database access request into a changed element in the matching result; the middleware routes the copied database access request to the new version database and routes the original database access request to the old version database.
In some embodiments, the middleware routing the database access request to the new version database or the old version database according to the matching result of the target access element further comprises: if the target access element is the changed element in the matching result, the middleware modifies the target access element in the copied database access request into the element before the change in the matching result; the middleware routes the copied database access request to the old version database and routes the original database access request to the new version database.
In some embodiments, the middleware routing the database access request to the new or old version database according to the matching result of the target access element comprises: and if the matching result of the target access element is empty, the middleware routes the database access request to the new database and the old database respectively.
In some embodiments, the method further comprises: constructing element change information between the new version database and the old version database by using the changed element in the new version database and the element before being changed in the corresponding old version database; and constructing a database change information table by utilizing various element change information between the new version database and the old version database.
According to another aspect of an embodiment of the present disclosure, there is provided middleware including: the request analysis module is configured to analyze the database access request sent by the application and obtain a target access element in the database access request; the information matching module is configured to match the database change information table by using the target access element to obtain a matching result of the target access element; the database change information table comprises various element change information between the new version database and the old version database, and the element change information comprises elements before change and elements after change; and the routing module is configured to route the database access request to the new version database or the old version database according to the matching result of the target access element.
In some embodiments, the matching result of the target access element is element change information corresponding to the target access element; the routing module includes: the request copying unit is configured to copy the database access request to obtain an original database access request and a copied database access request; a request modification unit configured to: if the target access element is an element before the change in the matching result, modifying the target access element in the copied database access request into a changed element in the matching result; a request routing unit configured to: and routing the copied database access request to the new version database, and routing the original database access request to the old version database.
In some embodiments, the request modification unit is further configured to: if the target access element is the changed element in the matching result, modifying the target access element in the copied database access request into the element before the change in the matching result; the request routing unit is further configured to: and routing the copied database access request to the old version database, and routing the original database access request to the new version database.
In some embodiments, the matching result for the target access element is null, the routing module configured to: and respectively routing the database access requests to the new version database and the old version database.
In some embodiments, the middleware further comprises an information table construction module configured to: constructing element change information between the new version database and the old version database by using the changed element in the new version database and the element before being changed in the corresponding old version database; and constructing a database change information table by utilizing various element change information between the new version database and the old version database.
According to another aspect of the embodiments of the present disclosure, there is provided an apparatus for accessing a database, including: a memory; and a processor coupled to the memory, the processor configured to perform the aforementioned method of accessing a database based on instructions stored in the memory.
According to yet another aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, which when executed by a processor, implement the aforementioned method of accessing a database.
According to the method and the device, the data distribution of the application to different databases can be realized on the premise of not modifying the application, so that the restriction of developing a new version application and a new version database is reduced, and the complexity of developing the new version application and the new version database is reduced.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
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 or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic diagram illustrating a data distribution flow in a conventional database gray scale distribution technology.
Fig. 2 is a schematic diagram illustrating a data publishing flow of the method for accessing a database according to the present disclosure.
FIG. 3 illustrates a flow diagram for some embodiments of building a database change information table.
FIG. 4 is a flow diagram illustrating some embodiments of a method of accessing a database according to the present disclosure.
Figure 5 illustrates a flow diagram of some embodiments in which middleware routes database access requests to a database.
Fig. 6 illustrates a structural schematic of some embodiments of an intermediate piece of the present disclosure.
Fig. 7 shows a schematic structural diagram of some embodiments of the apparatus for accessing a database of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
Fig. 1 is a schematic diagram illustrating a data distribution flow in a conventional database gray scale distribution technology. As shown in fig. 1, in the conventional database gray scale publishing technology, an old version of application needs to publish old version data to an old version database and a new version of database, and a new version of application needs to publish new version data to the old version database and the new version of database. The inventor researches and finds that the traditional database gray scale release technology has the following problems: on one hand, data distribution needs to be realized in an application layer, so that the complexity and workload of design and development are greatly increased; on the other hand, the data distribution code and the business logic code are mixed together, so that the code of the application layer is polluted and difficult to maintain.
To address these issues, the present disclosure adds a middleware layer between the application and the database instance. Fig. 2 is a schematic diagram illustrating a data publishing flow of the method for accessing a database according to the present disclosure. As shown in FIG. 2, both the new version application and the old version application access the new and old version database instances through middleware.
Before implementing the method for accessing the database of the present disclosure, a database change information table needs to be constructed. Some embodiments of constructing a database change information table are first described in conjunction with FIG. 3.
FIG. 3 illustrates a flow diagram for some embodiments of building a database change information table. As shown in fig. 3, the present embodiment includes steps S301 to S302.
In step S301, an element change message between the new version database and the old version database is constructed by using the changed element in the new version database and the element before being changed in the corresponding old version database.
For example, element change information between a new version database and an old version database may be defined through DSL (Domain-Specific Languages), and the element change information is defined from two dimensions of an element type and a new and an old version to describe a change policy of the new and old version database. For example, if a field is added to the new version of database based on the old version of database, the element type in the element change information is a field, the value of the old version is null, and the value of the new version is the name of the newly added field. For another example, if the new database modifies a field name based on the old database, the element type in the element modification information is a field, the old version value is the original field name, and the new version value is the new field name.
In step S302, a database change information table is constructed using the element change information between the new version database and the old version database.
Table 1 illustrates an example database change information table. Combining various element change information between the new version database and the old version database together to form a database change information table, so as to determine whether a target access element (a target element to be accessed by an SQL statement) in a database access request relates to change content between the new version database and the old version database by subsequently inquiring the database change information table.
TABLE 1
| Element type | Values of a new version database | Values of old version database |
| Field(s) | A | B |
| Field(s) | C | D |
| …… | …… | …… |
Some embodiments of the disclosed method of accessing a database are described below in conjunction with fig. 4.
FIG. 4 is a flow diagram illustrating some embodiments of a method of accessing a database according to the present disclosure. As shown in fig. 4, the present embodiment includes steps S401 to S403.
In step S401, the middleware parses the database access request sent by the application, and obtains a target access element in the database access request.
The database access requests sent by the application access data service comprise database access requests sent by the new version of application and database access requests sent by the old version of application. The middleware analyzes a database access request (visiting SQL statement) sent by an application, and can obtain a request type (including addition, deletion, modification and query) of the SQL statement, an object (including a table, a view, a function, a stored procedure and the like) contained in the SQL statement, and a field (including a query field and a condition field) contained in the SQL statement.
In step S402, the middleware matches the database change information table with the target access element, and obtains a matching result of the target access element.
The database change information table comprises various element change information between the new version database and the old version database, and the element change information comprises elements before change and elements after change. For example, if the target access element is a, the matching result is (field, a, B); for another example, if the target access element is D, the matching result is (field, C, D).
In step S403, the middleware routes the database access request to the new version database or the old version database according to the matching result of the target access element.
The process of the middleware in step S403 routing the database access request to the database is described below with reference to fig. 5. Figure 5 illustrates a flow diagram of some embodiments in which middleware routes database access requests to a database. As shown in fig. 5, the present embodiment includes steps S5031 to S5037.
In step S5030, the middleware determines whether the matching is successful.
And the middleware determines whether the content in the SQL request statement needs to be modified according to the matching result of the target access element in the SQL request statement and the database change information table. That is, the middleware determines whether each element in the SQL request statement relates to each item of element change information between the new version database and the old version database.
And if the matching is successful, the matching result of the target access element is the element change information corresponding to the target access element. That is, the target access element relates to a change, the SQL request statement needs to be modified, and the condition of modifying the SQL request statement determines the routing end point of the SQL request statement. Step S5031 is executed according to this case.
In step S5031, the middleware copies the database access request to obtain the original database access request and the copied database access request.
In step S5032, the middleware determines whether the target access element is an element before change in the matching result or an element after change.
If the target access element is an element before the change in the matching result, step S5033 to step S5034 are performed.
In step S5033, the middleware modifies the target access element in the copied database access request to the changed element in the matching result.
Those skilled in the art will appreciate that the present embodiment also supports the addition or deletion of elements such as tables, fields, etc. If a new version of the database has a newly added field on the basis of an old version of the database, the newly added field in the database access request may be removed.
In step S5034, the middleware routes the copied database access request to the new version database and routes the original database access request to the old version database.
If the target access element is an element changed in the matching result, step S5035 to step S5036 are executed.
In step S5035, the middleware modifies the target access element in the copied database access request to an element before change in the matching result.
In step S5036, the middleware routes the copied database access request to the old version database and routes the original database access request to the new version database.
And if the matching fails, the matching result of the target access element is empty. That is, the target access element does not involve changes, and the SQL request statement does not need to be modified. In which case the database access request is routed directly.
In this case, step S5037 is executed.
In step S5037, the middleware routes the database access request to the new version database and the old version database, respectively.
In the embodiment, the data distribution of the application to different databases can be realized on the premise of not modifying the application by utilizing the pre-established database change information table and matching with the analysis, matching, dynamic modification and dynamic routing of the middleware to the SQL request. Therefore, the method and the device do not need to add codes related to data distribution in an application layer, reduce the restriction of developing the new version application and the new version database, and reduce the complexity of developing the new version application and the new version database.
Some embodiments of the middleware of the present disclosure are described below in conjunction with fig. 6.
Fig. 6 illustrates a structural schematic of some embodiments of an intermediate piece of the present disclosure. As shown in fig. 6, the middleware 60 in the present embodiment includes:
the request analysis module 601 is configured to analyze a database access request sent by an application, and obtain a target access element in the database access request; the information matching module 602 is configured to match the database change information table with the target access element to obtain a matching result of the target access element; the database change information table comprises various element change information between the new version database and the old version database, and the element change information comprises elements before change and elements after change; and the routing module 603 is configured to route the database access request to the new database or the old database according to the matching result of the target access element.
In some embodiments, the matching result of the target access element is element change information corresponding to the target access element; the routing module 603 includes: a request copying unit 6031 configured to copy the database access request, obtaining an original database access request and a copied database access request; a request modification unit 6032 configured to: if the target access element is an element before the change in the matching result, modifying the target access element in the copied database access request into a changed element in the matching result; a request routing unit 6033 configured to: and routing the copied database access request to the new version database, and routing the original database access request to the old version database.
In some embodiments, the request modification unit 6032 is further configured to: if the target access element is the changed element in the matching result, modifying the target access element in the copied database access request into the element before the change in the matching result; the request routing unit 6033 is further configured to: and routing the copied database access request to the old version database, and routing the original database access request to the new version database.
In some embodiments, the matching result of the target access element is null, the routing module 603 is configured to: and respectively routing the database access requests to the new version database and the old version database.
In the embodiment, the data distribution of the application to different databases can be realized on the premise of not modifying the application by utilizing the pre-established database change information table and matching with the analysis, matching, dynamic modification and dynamic routing of the middleware to the SQL request. Therefore, the method and the device do not need to add codes related to data distribution in an application layer, reduce the restriction of developing the new version application and the new version database, and reduce the complexity of developing the new version application and the new version database.
In some embodiments, the middleware further comprises an information table construction module 600 configured to: constructing element change information between the new version database and the old version database by using the changed element in the new version database and the element before being changed in the corresponding old version database; and constructing a database change information table by utilizing various element change information between the new version database and the old version database.
Some embodiments of the apparatus for accessing a database of the present disclosure are described below in conjunction with fig. 7.
Fig. 7 shows a schematic structural diagram of some embodiments of the apparatus for accessing a database of the present disclosure. As shown in fig. 7, the apparatus 70 for accessing a database of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710, the processor 720 being configured to perform a method of accessing a database in any of the embodiments described above based on instructions stored in the memory 710.
The means for accessing a database 70 may further comprise an input output interface 730, a network interface 740, a storage interface 750, etc. These interfaces 730, 740, 750, as well as the memory 710 and the processor 720, may be connected, for example, by a bus 760. The input/output interface 730 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 740 provides a connection interface for various networking devices. The storage interface 750 provides a connection interface for external storage devices such as an SD card and a usb disk.
The present disclosure also includes a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement a method of accessing a database in any of the foregoing embodiments.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (12)
1. A method of accessing a database, comprising:
the middleware analyzes a database access request sent by an application to obtain a target access element in the database access request;
the middleware utilizes the target access element to match a database change information table to obtain a matching result of the target access element; the database change information table comprises various element change information between a new version database and an old version database, wherein the element change information comprises elements before change and elements after change;
and the middleware routes the database access request to a new version database or an old version database according to the matching result of the target access element.
2. The method of claim 1, wherein the matching result of the target access element is element change information corresponding to the target access element;
the middleware routing the database access request to a new version database or an old version database according to the matching result of the target access element comprises:
the middleware copies the database access request to obtain an original database access request and a copied database access request;
if the target access element is an element before the change in the matching result, the middleware modifies the target access element in the copied database access request into a changed element in the matching result; the middleware routes the copied database access request to the new version database and routes the original database access request to the old version database.
3. The method of claim 2, wherein the middleware routing the database access request to a new or old version of the database based on the matching of the target access element further comprises:
if the target access element is the changed element in the matching result, the middleware modifies the target access element in the copied database access request into the element before the change in the matching result; the middleware routes the copied database access request to the old version database and routes the original database access request to the new version database.
4. The method of claim 1, wherein the middleware routing the database access request to a new or old version database according to the matching result of the target access element comprises:
and if the matching result of the target access element is empty, the middleware respectively routes the database access request to the new database and the old database.
5. The method of claim 1, further comprising:
constructing element change information between the new version database and the old version database by using the changed element in the new version database and the element before being changed in the corresponding old version database;
and constructing a database change information table by utilizing various element change information between the new version database and the old version database.
6. An intermediary, comprising:
the request analysis module is configured to analyze a database access request sent by an application and obtain a target access element in the database access request;
the information matching module is configured to match a database change information table by using the target access element to obtain a matching result of the target access element; the database change information table comprises various element change information between a new version database and an old version database, wherein the element change information comprises elements before change and elements after change;
and the routing module is configured to route the database access request to a new version database or an old version database according to the matching result of the target access element.
7. The middleware of claim 6, wherein the matching result of the target access element is element change information corresponding to the target access element;
the routing module includes:
the request copying unit is configured to copy the database access request to obtain an original database access request and a copied database access request;
a request modification unit configured to: if the target access element is an element before the change in the matching result, modifying the target access element in the copied database access request into a changed element in the matching result;
a request routing unit configured to: and routing the copied database access request to the new version database, and routing the original database access request to the old version database.
8. An intermediary as in claim 6, wherein,
the request modification unit is further configured to: if the target access element is the changed element in the matching result, modifying the target access element in the copied database access request into the element before the change in the matching result;
the request routing unit is further configured to: and routing the copied database access request to the old version database, and routing the original database access request to the new version database.
9. The middleware of claim 6, wherein the matching result for the target access element is null, the routing module configured to: and respectively routing the database access request to a new database and an old database.
10. The middleware of claim 6, further comprising an information table building module configured to:
constructing element change information between the new version database and the old version database by using the changed element in the new version database and the element before being changed in the corresponding old version database; and constructing a database change information table by utilizing various element change information between the new version database and the old version database.
11. An apparatus for accessing a database, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the method of accessing a database of any of claims 1-5 based on instructions stored in the memory.
12. A computer readable storage medium, wherein the computer readable storage medium stores computer instructions which, when executed by a processor, implement a method of accessing a database as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911172693.1A CN112948454A (en) | 2019-11-26 | 2019-11-26 | Method, device, middleware and computer readable storage medium for accessing database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911172693.1A CN112948454A (en) | 2019-11-26 | 2019-11-26 | Method, device, middleware and computer readable storage medium for accessing database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112948454A true CN112948454A (en) | 2021-06-11 |
Family
ID=76224931
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911172693.1A Pending CN112948454A (en) | 2019-11-26 | 2019-11-26 | Method, device, middleware and computer readable storage medium for accessing database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112948454A (en) |
-
2019
- 2019-11-26 CN CN201911172693.1A patent/CN112948454A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11106816B2 (en) | Database public interface | |
| JP5598017B2 (en) | Judgment program, method and apparatus | |
| US9229952B1 (en) | History preserving data pipeline system and method | |
| US9519642B2 (en) | System, method and computer program product for multilingual content management | |
| US20180239796A1 (en) | Multi-tenant distribution of graph database caches | |
| US20220284102A1 (en) | Data lineage management | |
| US7895156B2 (en) | Method, system, and computer program product for implementing a model exchange framework generating a synchronization record in response to a model exchange request using fusion technology | |
| US20190197130A1 (en) | Ensuring consistency in distributed incremental content publishing | |
| CN117609183A (en) | System and method for database tenant migration | |
| US20230161746A1 (en) | Data pipeline branching | |
| US20090234880A1 (en) | Remote storage and management of binary object data | |
| US20170161511A1 (en) | Database public interface | |
| US10754971B2 (en) | Referenced access control list | |
| US8782631B2 (en) | Copy management of process versions over lifecycle | |
| CN111858615A (en) | Database table generation method, system, computer system and readable storage medium | |
| CN111881223A (en) | Data management method, device, system and storage medium | |
| KR102172255B1 (en) | Method and apparatus for executing distributed computing tasks | |
| US20200342008A1 (en) | System for lightweight objects | |
| US20130173229A1 (en) | Computer aided modeling | |
| CN111427577A (en) | Code processing method and device and server | |
| CN110222047A (en) | A kind of dynamic list generation method and device | |
| US20170177686A1 (en) | Property models on mobile devices | |
| US20080275959A1 (en) | Distributed Search in a Casual Network of Servers | |
| US9009731B2 (en) | Conversion of lightweight object to a heavyweight object | |
| US10936572B2 (en) | Method, apparatus, and computer program product for improved tracking of state data |
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 |