CN113535843B - Data query method and device, electronic equipment and readable storage medium - Google Patents
Data query method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113535843B CN113535843B CN202111077435.2A CN202111077435A CN113535843B CN 113535843 B CN113535843 B CN 113535843B CN 202111077435 A CN202111077435 A CN 202111077435A CN 113535843 B CN113535843 B CN 113535843B
- Authority
- CN
- China
- Prior art keywords
- database
- table name
- sql statement
- target
- name information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
-
- 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/242—Query formulation
- G06F16/2433—Query languages
-
- 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/2453—Query optimisation
- G06F16/24534—Query rewriting; Transformation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a data query method, a data query device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: acquiring a first SQL statement; analyzing the first SQL statement to acquire target table name information, wherein the target table name information comprises a table name and information of at least one database except the target database in a database set; creating an external table according to the target table name information; replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement; and executing the second SQL statement. The method and the device can improve the efficiency of data query.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a data query method and apparatus, an electronic device, and a readable storage medium.
Background
Currently, various databases have the ability to access external data, which may be in various forms, such as text, web pages, databases, etc. However, when various databases access external data, the databases have a set of grammar rules, that is, the external access is realized in various ways without a unified standard, and when different types of databases are switched to access the external databases, the corresponding grammar rules need to be learned and switched, so that the efficiency is low.
Disclosure of Invention
The application provides a data query method, a data query device, electronic equipment and a readable storage medium, which aim to solve the problem of low query efficiency.
In a first aspect, an embodiment of the present application provides a data query method, including:
acquiring a first SQL statement;
analyzing the first SQL statement to acquire target table name information, wherein the target table name information comprises a table name and information of at least one database except the target database in a database set;
creating an external table according to the target table name information;
replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement;
and executing the second SQL statement.
In a second aspect, an embodiment of the present application further provides a data query apparatus, including:
the acquisition module is used for acquiring a first SQL statement;
the analysis module is used for analyzing the first SQL statement to acquire target table name information, and the target table name information comprises a table name and information of at least one database except the target database in a database set;
the creating module is used for creating an external table according to the target table name information;
the replacing module is used for replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement;
And the execution module is used for executing the second SQL statement.
In a third aspect, an embodiment of the present application further provides an electronic device, including: the data query method includes a memory, a processor, and a program or instructions stored in the memory and executable on the processor, where the program or instructions implement the steps of the data query method disclosed in the first aspect of the embodiments of the present application when executed by the processor.
In a fourth aspect, an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements the steps in the data query method disclosed in the first aspect of the embodiment of the present application.
In the embodiment of the application, the first SQL statement is obtained and analyzed to obtain target table name information, the target table name information comprises table names and information of at least one database except the target database in a database set, an external table is created according to the target table name information, the table names in the target table name information are replaced by the table names of the external table to generate a second SQL statement, and then the second SQL statement is executed, so that joint query of database cross-instances can be achieved, external data access modes of the database are simplified and unified, and accordingly data query efficiency can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a data query method provided in an embodiment of the present application;
FIG. 2 is a second flowchart of a data query method according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a data query device according to an embodiment of the present application;
fig. 4 is a second schematic structural diagram of a data query device according to an embodiment of the present application;
fig. 5 is a third schematic structural diagram of a data query apparatus according to an embodiment of the present application;
FIG. 6 is a fourth schematic structural diagram of a data query device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," and the like in the embodiments of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Further, as used herein, "and/or" means at least one of the connected objects, e.g., a and/or B and/or C, means 7 cases including a alone, B alone, C alone, and both a and B present, B and C present, both a and C present, and A, B and C present.
Referring to fig. 1, fig. 1 is a schematic flow chart of a data query method according to an embodiment of the present application, as shown in fig. 1, including the following steps:
The obtaining may be obtained by a pre-selected database server, for example: the database server may simply extend the input SQL statement by receiving the SQL (Structured Query Language) statement, and standardize a method for representing the SQL statement, so as to analyze the obtained SQL statement in the following.
And 102, analyzing the first SQL statement to acquire target table name information, wherein the target table name information comprises a table name and information of at least one database except the target database in a database set.
The target database may represent a database corresponding to a database server executing SQL statements, and at least one database other than the target database in the database set may represent databases of other database servers, that is, when the first SQL statement is executed to include cross-database joint query of a cross-instance, target table name information corresponding to the at least one database may be obtained by analyzing the first SQL statement. Specifically, the target table name information may further include information such as an address and a user name and a password, so that a corresponding external table may be created according to the information.
In addition, the database set may be a set of databases that need to be queried to execute the first SQL statement, for example: the first SQL statement requires querying three databases: A. b and C, if the database a is a target database, and the database B and the database C are two databases other than the target database, the target table name information includes target table name information corresponding to the database B and the database C, respectively.
And 103, creating an external table according to the target table name information.
The external table may correspond to the at least one database one to one, for example: if the first SQL statement is analyzed, and the two databases in the acquired database set are databases other than the target database, corresponding external tables can be created according to the two databases.
And 104, replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement.
It can be understood that the table names of the replaced external tables and the table names of the databases creating the external tables are also in one-to-one correspondence, and by replacing all database table names except the target database in the first SQL statement with the correspondingly created external table names, the database server can execute the SQL statement in a unified manner.
And 105, executing the second SQL statement.
Specifically, in the process of creating the external table and replacing the table name in the target table name information with the table name of the corresponding external table, a plurality of SQL statements are generated, for example: creating SQL sentences linked by a database, creating SQL sentences of an external table and the like, and after the SQL sentences returning results are executed, correspondingly deleting the SQL sentences linked by the database, deleting the SQL sentences of the external table and the like. If a plurality of SQL statements are generated in the process, the plurality of SQL statements may be sequentially executed, but when a result is returned, only an execution result of the second SQL statement may be returned, and execution results of other SQL statements may be discarded, and the second SQL statement may represent an SQL statement corresponding to a table name of the external table among the plurality of SQL statements.
In the embodiment of the application, the first SQL statement is obtained and analyzed to obtain target table name information, the target table name information comprises table names and information of at least one database except the target database in a database set, an external table is created according to the target table name information, the table names in the target table name information are replaced by the table names of the external table to generate a second SQL statement, and then the second SQL statement is executed, so that joint query of database cross-instances can be achieved, external data access modes of the database are simplified and unified, and accordingly data query efficiency can be improved.
In addition, the first SQL sentence is analyzed to obtain target table name information, the table name in the target table name information is replaced by the table name of the external table, and database cross-instance query is realized in a mode of executing the second SQL sentence, so that the method is simple and convenient for a user, and the learning cost can be reduced.
Optionally, the parsing the first SQL statement to obtain the target table name information in step 102 may specifically include:
converting the table name format in the first SQL statement into a preset format, wherein the preset format comprises an instance name, a library name, a mode and a table name;
And analyzing the first SQL statement in the preset format to acquire the target table name information.
Specifically, the preset format may be a preset format convenient for identifying the SQL statement, for example: by standardizing the table name format in the SQL statement, the table name information in the SQL statement can be quickly analyzed, and the connection information, the user name and the password of the instance can be acquired. The SQL sentences with the preset formats comprise instance names, library names, patterns and table names, each replaced external table can correspond to a database table consisting of a group of instance names, library names, patterns and table name formats, and target table name information required to be acquired by data query is determined through each group of the instance names, library names, patterns and table names with the preset formats.
In this embodiment, by converting the table name format in the first SQL statement into a preset format, at least one database other than the target database in the first SQL statement can be quickly determined and identified, so as to create an external table according to the acquired target table name information, thereby implementing cross-instance query of data.
Optionally, the analyzing the first SQL statement in the preset format to obtain the target table name information may include:
Identifying the database set in the first SQL statement in the preset format;
determining the at least one database in the database set except the target database according to the instance name and the library name;
and acquiring the target table name information corresponding to the at least one database.
The database type in the database set may be any, for example: may include the same type of database or may include different types of databases.
According to the first SQL statement with the preset format, a database set to be executed in the first SQL statement can be found out, and is analyzed, and connection information, a user name and a password, a database table and a table name of an instance are found out. Thus, for different instances of the database, corresponding external tables may be created.
In this embodiment, the target table name information to be replaced may be quickly determined by determining the at least one database other than the target database in the database set and acquiring the target table name information corresponding to the at least one database.
Optionally, the creating an external table according to the target table name information in step 103 may specifically include:
Obtaining a database type corresponding to the at least one database according to the target table name information;
and creating the external table by using an external access interface corresponding to the database type.
The external access interface is implemented differently on different types of databases as an SQL standard, for example: for postgresql may be implemented using either the dblink or postgres _ fdw components. When various databases access external data, the databases have a set of grammar rules. For databases of different instances, the creation of the external table is implemented using a corresponding FDW (Foreign Data Wrapper) external access interface.
In this embodiment, the external table corresponding to the at least one database may be created by creating the external table using the external access interface corresponding to the database type, and the external table name is used to replace the target table name information in the first SQL statement, thereby implementing a cross-instance join query for different databases.
The various optional implementations described in the embodiments of the present application may be implemented in combination with each other or implemented separately without conflicting with each other, and the embodiments of the present application are not limited to this.
For ease of understanding, the examples are illustrated below:
referring to fig. 2, fig. 2 is a second schematic flowchart of a data query method according to an embodiment of the present application, and as shown in fig. 2, the method may include the following steps:
acquiring an SQL statement;
identifying "instance name, library name, schema, table name" in an SQL statement;
creating an external table corresponding to the example name, the library name, the mode and the table name;
replacing a table in the format of 'instance name, library name, mode and table name' in an SQL statement with a corresponding external table;
executing the SQL statement;
and returning an execution result.
The table in the obtained SQL statement may be represented in the format of "instance name, library name, schema, table name", and all tables in the format of "instance name, library name, schema, table name" in the SQL statement are found and analyzed, and the connection information, username and password, database table, and table name of the instance are found, so that corresponding external access interfaces may be used for databases of different instances to implement creation of an external table.
Specifically, the specific steps of the execution process of the data query method are as follows:
selecting a target database, namely a database server executing SQL statements;
analyzing the SQL statement, and converting the SQL statement: and identifying cross-instance cross-database outside the target server according to the table name format of 'instance name, library name, mode and table name'. For different types of databases, executing different cross-database and cross-instance combined query modes to create an external table, and finally converting all table names in the format of 'instance name, library name, mode, table name' into created external table names;
And the target database server executes the SQL statement and returns the result. The converted SQL statement may become multiple, and generally only one of the multiple SQL statements returns a result. For a plurality of SQL sentences generated after conversion, the plurality of SQL sentences can be sequentially executed, the SQL sentence execution result needing to return the result is returned, and the results of other sentences are discarded. It can be understood that the SQL statements to which results need to be returned are the SQL statements corresponding to the created external table names instead.
Taking postgresql as an example, the obtained SQL statement is:
select * from a.traffic_survey.public.app_user,b.fcd.public.sys_user；
wherein: a. b represents a database instance, correspondingly, traffic _ surveyy can represent a corresponding library name under a, fcd can represent a corresponding library name under b, which libraries can be checked under the instance, public is fixed, and app _ user and sys _ user are corresponding table names; and a can also be replaced by b, c, d, and traffic _ reserve can be replaced by corresponding library names under b, c and d, and the corresponding examples can be accessed, and which tables are checked under the corresponding libraries.
The specific implementation process of the data query method is as follows:
transforming the tables a.traffic _ reported.public.app _ user, b.fcd.public.sys _ user into external tables on the target server executing in sql, which may be implemented by the extension component postgres _ fdw; wherein a and b represent instance names, and the connection information can be obtained through the existing static information;
Corresponding tables a.traffic _ resource.public.app _ user and b.fcd.public.sys _ user in the SQL statement to external tables on the target server are respectively marked as table1 and table2, then the SQL statement is changed to select from table1 and table 2.
The SQL statement select from table1, table2 is executed on the target server and the result is returned.
Therefore, the database cross-instance joint query can be realized by simply extending the representation method in the standard SQL sentence, the external data access mode of the database is simplified and unified, the database cross-instance or heterogeneous access is realized, and the database cross-instance or heterogeneous access is simple and convenient for users, and the learning cost is low.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a data query apparatus according to an embodiment of the present disclosure, and as shown in fig. 3, the apparatus 300 includes:
an obtaining module 301, configured to obtain a first SQL statement;
the parsing module 302 is configured to parse the first SQL statement to obtain target table name information, where the target table name information includes a table name and information of at least one database in a database set except for a target database;
a creating module 303, configured to create an external table according to the target table name information;
a replacing module 304, configured to replace a table name in the target table name information with a table name of the external table, so as to generate a second SQL statement;
The execution module 305 is configured to execute the second SQL statement.
Optionally, as shown in fig. 4, the parsing module 302 may specifically include:
a converting unit 3021, configured to convert a table name format in the first SQL statement into a preset format, where the preset format includes an instance name, a library name, a schema, and a table name;
an analyzing unit 3022, configured to analyze the first SQL statement in the preset format to obtain the target table name information.
Optionally, as shown in fig. 5, the parsing unit 3022 may specifically include:
an identifying subunit 30221, configured to identify the database set in the first SQL statement in the preset format;
a determining subunit 30222, configured to determine the at least one database in the database set other than the target database according to the instance name and the library name;
an obtaining subunit 30223, configured to obtain the target table name information corresponding to the at least one database.
Optionally, as shown in fig. 6, the creating module 303 may specifically include:
an obtaining unit 3031, configured to obtain, according to the target table name information, a database type corresponding to the at least one database;
a creating unit 3032, configured to create the external table using the external access interface corresponding to the database type.
The data query device 300 can implement each process of the method embodiment in fig. 1 in the embodiment of the present application, and achieve the same beneficial effects, and for avoiding repetition, the details are not described here again.
Referring to fig. 7, an electronic device 700 includes a processor 701, a memory 702, and a program or an instruction stored in the memory 702 and executable on the processor 701, where the program or the instruction when executed by the processor 701 implements the processes of the method embodiment in fig. 1 in the embodiment of the present application, and can achieve the same technical effects, and therefore, the descriptions thereof are omitted here to avoid repetition.
Those skilled in the art will appreciate that all or part of the steps of the method according to the above embodiments may be implemented by hardware associated with program instructions, and the program may be stored in a readable medium.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the method embodiment in fig. 1 in the embodiment of the present application, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The processor is the processor in the electronic device in the above embodiment. Readable storage media, including computer-readable storage media, such as Read-Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods of the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (6)
1. A method for querying data, comprising:
acquiring a first SQL statement;
analyzing the first SQL statement to acquire target table name information, wherein the target table name information comprises a table name and information of at least one database except the target database in a database set;
creating an external table according to the target table name information;
replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement;
executing the second SQL statement;
the analyzing the first SQL statement to obtain the target table name information comprises:
converting a table name format in the first SQL statement into a preset format, wherein the preset format comprises an instance name, a library name, a mode and a table name;
analyzing the first SQL statement in the preset format to acquire the target table name information;
the creating of the external table according to the target table name information includes:
acquiring a database type corresponding to the at least one database according to the target table name information;
and creating the external table by using an external access interface corresponding to the database type.
2. The method of claim 1, wherein said parsing said first SQL statement in said preset format to obtain said target table name information comprises:
Identifying the database set in the first SQL statement in the preset format;
determining the at least one database in the database set except the target database according to the instance name and the library name;
and acquiring the target table name information corresponding to the at least one database.
3. A data query apparatus, comprising:
the acquisition module is used for acquiring a first SQL statement;
the analysis module is used for analyzing the first SQL statement to acquire target table name information, and the target table name information comprises a table name and information of at least one database except the target database in a database set;
the creating module is used for creating an external table according to the target table name information;
the replacing module is used for replacing the table name in the target table name information with the table name of the external table to generate a second SQL statement;
the execution module is used for executing the second SQL statement;
the parsing module includes:
the conversion unit is used for converting the table name format in the first SQL statement into a preset format, and the preset format comprises an instance name, a library name, a mode and a table name;
the analysis unit is used for analyzing the first SQL statement in the preset format to acquire the target table name information;
The creation module comprises:
the acquisition unit is used for acquiring the database type corresponding to the at least one database according to the target table name information;
and the creating unit is used for creating the external table by using an external access interface corresponding to the database type.
4. The apparatus of claim 3, wherein the parsing unit comprises:
the identification subunit is used for identifying the database set in the first SQL statement in the preset format;
a determining subunit, configured to determine, according to the instance name and the library name, the at least one database in the database set other than the target database;
and the obtaining subunit is configured to obtain the target table name information corresponding to the at least one database.
5. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executed on the processor, which when executed by the processor, implement the steps of the data query method of any one of claims 1 to 2.
6. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the data query method of any one of claims 1 to 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111077435.2A CN113535843B (en) | 2021-09-15 | 2021-09-15 | Data query method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111077435.2A CN113535843B (en) | 2021-09-15 | 2021-09-15 | Data query method and device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535843A CN113535843A (en) | 2021-10-22 |
| CN113535843B true CN113535843B (en) | 2022-07-29 |
Family
ID=78093244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111077435.2A Active CN113535843B (en) | 2021-09-15 | 2021-09-15 | Data query method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535843B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777278A (en) * | 2016-12-29 | 2017-05-31 | 海尔优家智能科技（北京）有限公司 | A kind of data processing method and device based on Spark |
| CN110837515A (en) * | 2019-11-06 | 2020-02-25 | 北京天融信网络安全技术有限公司 | Database-based data processing method and electronic equipment |
| CN111078728A (en) * | 2019-12-19 | 2020-04-28 | 山大地纬软件股份有限公司 | Cross-database query method and device in database filing mode |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101685449B (en) * | 2008-09-26 | 2012-07-11 | 国际商业机器公司 | Method and system for connecting tables in a plurality of heterogeneous distributed databases |
| CN106598977A (en) * | 2015-10-15 | 2017-04-26 | 北京国双科技有限公司 | Data migration method and device |
-
2021
- 2021-09-15 CN CN202111077435.2A patent/CN113535843B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777278A (en) * | 2016-12-29 | 2017-05-31 | 海尔优家智能科技（北京）有限公司 | A kind of data processing method and device based on Spark |
| CN110837515A (en) * | 2019-11-06 | 2020-02-25 | 北京天融信网络安全技术有限公司 | Database-based data processing method and electronic equipment |
| CN111078728A (en) * | 2019-12-19 | 2020-04-28 | 山大地纬软件股份有限公司 | Cross-database query method and device in database filing mode |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535843A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062952B (en) | Data query method and device and electronic equipment | |
| CN106611044B (en) | SQL optimization method and equipment | |
| US9037552B2 (en) | Methods for analyzing a database and devices thereof | |
| CN110909010B (en) | Data intelligent analysis configuration management method, device, equipment and storage medium | |
| US20110078203A1 (en) | System and method for application navigation | |
| CN112579610A (en) | Multi-data source structure analysis method, system, terminal device and storage medium | |
| CN116821103B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN110737689A (en) | Data standard conformance detection method, device, system and storage medium | |
| CN111198898A (en) | Big data query method and big data query device | |
| CN111427784A (en) | Data acquisition method, device, equipment and storage medium | |
| CN111090665A (en) | Data task scheduling method and scheduling system | |
| CN111209325A (en) | Service system interface identification method, device and storage medium | |
| CN108008947B (en) | Intelligent prompting method and device for programming statement, server and storage medium | |
| CN110188432B (en) | System architecture verification method, electronic device and computer-readable storage medium | |
| CN113535843B (en) | Data query method and device, electronic equipment and readable storage medium | |
| CN110188106B (en) | Data management method and device | |
| CN114547083A (en) | Data processing method and device and electronic equipment | |
| CN114358596A (en) | Index calculation method and device | |
| CN105677827B (en) | A kind of acquisition methods and device of list | |
| CN113626470A (en) | ElasticSearch query method, device, equipment and readable storage medium | |
| US11328018B2 (en) | System and method for state dependency based task execution and natural language response generation | |
| CN110147477B (en) | Data resource modeling extraction method, device and equipment of Web system | |
| CN108629012B (en) | Intelligent verification method and system for forensic data analysis accuracy | |
| CN112579600A (en) | Data processing method and device based on vehicle-mounted question answering | |
| CN113190579B (en) | Method, device and system for constructing and querying virtual data view and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |