CN103729471A - Method and device for database query - Google Patents
Method and device for database query Download PDFInfo
- Publication number
- CN103729471A CN103729471A CN201410027522.0A CN201410027522A CN103729471A CN 103729471 A CN103729471 A CN 103729471A CN 201410027522 A CN201410027522 A CN 201410027522A CN 103729471 A CN103729471 A CN 103729471A
- Authority
- CN
- China
- Prior art keywords
- inquiry
- data
- query
- database server
- buffer memory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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
Abstract
The embodiment of the invention provides a method and a device for database query. The method for database query comprises the following steps: receiving a query request sent by the client of a database, wherein the query request includes query identification (ID) and query parameters; determining a query plan storage in advance according to the query ID; carrying out data query on data cached in advance according to the query parameters and the determined query plane; sending a query result to the client of the database. According to the technical scheme of the embodiment of the invention, the query efficiency is higher, and the method and the device are suitable for query with high concentration ratio and high performance.
Description
Technical field
The embodiment of the present invention relates to the communication technology, relates in particular to a kind of data base query method and device.
Background technology
Adopting in the business procession of data base querying, often to carry out high concentration degree and high performance inquiry to some particular data, data to be checked may need the inquiry of multilist association.Wherein, it is fewer that the inquiry of high concentration degree refers to that rule searching changes, and is all several class inquiries, and high performance inquiry refers to that this class search request responds fast, and the number of times of execution that needs per second is very many, for example 100,000 times or more.For instance, the inquiry of the unified view of customers of events marketing field to particular customer, its querying condition is exactly customer ID, and what Query Result returned is the attribute (containing sublist record) in specific some client's views.Streaming gathers for another example, and to each event, the target record of first association to gather, need to do High Performance Data Query equally.
In existing database inquiry mode, often based on Structured Query Language (SQL), (Structured Query Language, hereinafter to be referred as SQL) statement, realizes by associated multiple tables in this type of inquiry.During each inquiry, operation system can be delivered to database server by SQL statement and query argument, for example, can bring in this SQL statement of transmission and query argument by calling the database client being deployed in this operation system.Database server is resolved SQL statement, or reuses original inquiry plan, loads data from hard disk, or the data in use buffer memory, the association of executing data table waits sequence of operations, then to operation system, returns to Query Result, and returns to the metadata information of Query Result simultaneously.
But existing database inquiry mode is when processing this high concentration degree and high performance inquiry, processing power is limited, cannot meet user's demand.
Summary of the invention
The embodiment of the present invention provides a kind of data base query method and device.
First aspect, provides a kind of data base query method, comprising:
Receive the inquiry request that database client sends, in described inquiry request, comprise inquiry sign ID and query argument;
According to described inquiry ID, determine pre-stored inquiry plan;
According to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
To described database client, send Query Result.
Second aspect, provides another kind of data base query method, comprising:
To database server, send inquiry request, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Receive the Query Result that described database server sends.
The third aspect, provides a kind of database server, comprising:
Receiver module, the inquiry request sending for receiving database client, comprises inquiry sign ID and query argument in described inquiry request;
Determination module, for determining pre-stored inquiry plan according to described inquiry ID;
Enquiry module, for according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Sending module, for sending Query Result to described database client.
Fourth aspect, provides a kind of database client, comprising:
Sending module, for sending inquiry request to database server, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Receiver module, the Query Result sending for receiving described database server.
In the embodiment of the present invention, operation system can be passed through calling data storehouse client trade mark enquiries ID and the inquiry plan corresponding with this inquiry ID in database server in advance, and data query corresponding to this inquiry ID can also be buffered in internal memory in advance.When carrying out data query, database client only need to transmit inquiry ID and query argument to database server; For database server, utilize this inquiry ID can determine pre-stored inquiry plan, and according to query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance, and then to database client feedback query result.This data base querying process all needs to transmit SQL statement at every turn when inquiring about without same prior art, also without SQL statement is resolved, more without going again, in hard disk, carry out the operations such as data query and data structure organization after parsing, therefore, the technical scheme search efficiency of the present embodiment is higher, is applicable to high concentration degree and high performance inquiry.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the process flow diagram of data base query method embodiment mono-of the present invention;
Fig. 2 is the process flow diagram of data base query method embodiment bis-of the present invention;
Fig. 3 is the process flow diagram of data base query method embodiment tri-of the present invention;
Fig. 4 is the structural representation of database server embodiment mono-of the present invention;
Fig. 5 is the structural representation of database server embodiment bis-of the present invention;
Fig. 6 is the structural representation of database client embodiment of the present invention.
Embodiment
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
Fig. 1 is the process flow diagram of data base query method embodiment mono-of the present invention, and as shown in Figure 1, the method for the present embodiment can comprise:
The inquiry request that S101, reception database client send, comprises inquiry sign ID and query argument in described inquiry request;
S102, according to described inquiry ID, determine pre-stored inquiry plan;
S103, according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
S104, to described database client, send Query Result.
In the present embodiment, inquiry ID is that operation system is passed through database client and in database server, registered in advance, and this database client can be deployed in operation system.When operation system starts, or when business rule changes, operation system need to be initiated the pre-registration of inquiry, and operation system is informed database client inquiry ID and corresponding query logic, and database client is informed database server inquiry ID and corresponding query logic.Then, the query logic that database server can be based on corresponding, is loaded into the data in advance that will inquire about in buffer memory, and according to query logic, organizes the structure of data to be checked.Optionally, database server can carry out complex optimum to the structure of data in conjunction with multiple different inquiry ID.For example merge similarly inquiry, merge identical incidence relation etc., allow multiple queries share index structure and data cached.Then, database server can generate inquiry plan corresponding to this inquiry ID.Preferably, database server can feed back to database client by the metadata structure corresponding data of buffer memory, when subsequent query, without all will feed back metadata structure at every turn, and only need to return to actual data like this.
For instance, operation system will be done three different inquiries: the attribute that first inquiry will be inquired about is dispersed in three tables, comprises a master meter and two 1:N sublists; The attribute that second inquiry will be inquired about is all in a master meter; The 3rd attribute that inquiry will be inquired about is all in 1 1:N sublist.It is 101,102,103 that operation system is distributed respectively inquiry ID to these three inquiries, then constructs these three query logics (may be also just determine the system development phase, or system performance rules calculating based on system convention after changing).If wherein first query logic represents with SQL, need three SQL statement, after two be respectively a SQL statement, the attribute description information that each query logic comprises the corresponding data of inquiring about of inquiry ID institute.Operation system can pass to database client by inquiry ID and corresponding query logic, and then passes to database server by database client.Database server can be according to this query logic organising data, for example, for 101 this inquiry ID, need to a master meter be carried out associated with two 1:N sublists, then data in advance is carried out to buffer memory, and generate the inquiry plan corresponding with inquiry sign, this inquiry plan described based on database client transmission and the concrete inquiry mode of query argument while carrying out data query.
When data query, database server can receive the inquiry request that database client sends, and can comprise inquiry ID and query argument in this inquiry request.Wherein, query argument is the inquiry ID registering in database server in advance, and query argument can be for example the suction parameters such as customer ID.Then, database server can be based on inquiry ID, determine the pre-stored inquiry plan corresponding with this inquiry ID, thereby can determine based on this query argument, specifically data query how, be that database server can be according to query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance, thus can obtain query structure.Finally, database server can be to database client feedback query result.
In the present embodiment, operation system can be passed through calling data storehouse client trade mark enquiries ID and the inquiry plan corresponding with this inquiry ID in database server in advance, and data query corresponding to this inquiry ID can also be buffered in internal memory in advance.When carrying out data query, database client only need to transmit inquiry ID and query argument to database server; For database server, utilize this inquiry ID can determine pre-stored inquiry plan, and according to query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance, and then to database client feedback query result.This data base querying process all needs to transmit SQL statement at every turn when inquiring about without same prior art, also without SQL statement is resolved, more without going again, in hard disk, carry out the operations such as data query and data structure organization after parsing, therefore, the technical scheme search efficiency of the present embodiment is higher, is more suitable for high concentration degree and high performance inquiry.
Adopt a specific embodiment below, embodiment of the method one shown in Fig. 1 is elaborated.
Fig. 2 is the process flow diagram of data base query method embodiment bis-of the present invention, and as shown in Figure 2, the method for the present embodiment can comprise:
S201, receive inquiry ID and query logic that database client sends, in this query logic, comprise inquiry ID the attribute description information of corresponding data query.
For instance, if will inquire about 50 attributes of unified view of customers, these 50 property distribution in 5 tables, every table 10 attribute, wherein 2 tables are 1:N associations, other three tables are 1:1 associations.Query argument is customer ID.For rule-based system, operation system can be directly informed the title of 50 attributes that database server will inquire about by calling data storehouse client.For the system based on SQL, this inquiry can split into three SQL, one is the association of three 1:1 tables, the independent inquiry of two 1:N tables in addition, operation system can provide an inquiry ID above inquiry, for example 101, and inquiry ID and corresponding query logic, tell database server by database client.
S202, data corresponding to attribute description information are carried out to buffer memory.
Database server can, according to attribute description information, carry out buffer memory by corresponding data in advance.
For the scene of multilist association, what S202 was concrete can, according to attribute description information, carry out association at least two tables of data, and associated tables of data is carried out to buffer memory.
Continuity precedent, database server can first be carried out incidence relation the table of three 1:1 associations, and corresponding row are loaded into internal memory, forms a memory table that has 30 attributes.Meanwhile, the table of two 1:N associations is also loaded into internal memory, in this memory table, adds two index column for 1:N table, point to the internal memory start address of the corresponding row of the associated table of two 1:N.
S203, generation inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan.
For instance, database server can create search index, for example Hash (Hash) index to having the 1:1 memory table of 50 attributes and the query key of two 1:N memory tables.Database server provides inquiry ID(101) corresponding inquiry plan, for example based on query argument, use Hash index, find corresponding row address, then copy 30 attributes of this row to output buffer, then respectively multirow record copies associated the address corresponding attribute in the twoth 1:N memory table is arrived to output buffer.
S204, to described database client, send the metadata structure corresponding with the data of described buffer memory.
This metadata structure, for example, be 30 1:1 attributes, and 2 sub-attributes of set eachly contain 10 attributes.
Above-mentioned S201～S204 has completed pre-registration process.
The inquiry request that S205, reception database client send, comprises inquiry sign ID and query argument in described inquiry request.
When database client is initiated an inquiry, server client can arrive database server to database server transmission inquiry ID " 101 " and query argument " 31059865321 ".
S206, according to described inquiry ID, determine pre-stored inquiry plan.
Database server can be inquired about ID " 101 " can determine aforementioned pre-stored inquiry plan.
S207, according to described query argument, determine search index;
Database server can, according to query argument " 31059865321 ", be determined Hash index.
S208, according to described search index, determine inquire address, and by described inquire address place preserve data copy output buffer to.
Database server, according to this Hash index, can be determined inquire address, for example row address in tables of data, thus the data that inquire address place can be preserved copy output buffer to.
For the scene of multilist association, database server, according to search index, may need to determine at least two inquire addresses, wherein, and the memory address in the corresponding tables of data of each inquire address; According to each inquire address, from corresponding tables of data, search data, and copy the data that find to output buffer from each tables of data.
S209, the data in output buffer are sent to described database client.
Database server finally can send to database client by the data in output buffer, thereby makes database client obtain the data of inquiring about, and the metadata structure obtaining in advance based on S204 can be known the data structure of the data of inquiry.
The present embodiment, in the process of registered in advance, operation system can be passed through calling data storehouse client trade mark enquiries ID and the inquiry plan corresponding with this inquiry ID in database server in advance, the data query that this inquiry ID is corresponding can also be buffered in internal memory in advance, and database server can also feed back to database client in advance by metadata structure.When carrying out data query, database client only need to transmit inquiry ID and query argument to database server, database server utilizes this inquiry ID can determine pre-stored inquiry plan, and according to query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance, and then to database client feedback query result, thereby make the metadata structure of database client based on obtaining in advance can know the data structure of the data of inquiry.This data base querying process all needs to transmit SQL statement at every turn when inquiring about without same prior art, also without SQL statement is resolved, more without going again, in hard disk, carry out the operations such as data query and data structure organization after parsing, and, database server just feeds back metadata structure once without every inquiry one secondary data, therefore, the technical scheme search efficiency of the present embodiment is higher, is more suitable for high concentration degree and high performance inquiry.
Fig. 3 is the process flow diagram of data base query method embodiment tri-of the present invention, and as shown in Figure 3, the method for the present embodiment can comprise:
S301, to database server send inquiry request, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
S302, receive the Query Result that described database server sends.
Further, before S301 sends inquiry request to database server, can also comprise:
To described database server, send inquiry ID and query logic, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query, so that described database server carries out buffer memory to data corresponding to described attribute description information, generate inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
Receive metadata structure corresponding to the data with described buffer memory that described database server sends.
The method of the present embodiment is database client performed method corresponding to method performed with database server in Fig. 1 and Fig. 2, and it realizes principle and technique effect is similar, repeats no more herein.
Fig. 4 is the structural representation of database server embodiment mono-of the present invention, and as shown in Figure 4, the database server of the present embodiment, comprising: receiver module 401, determination module 402, enquiry module 403, sending module 404, wherein:
Sending module 404, for sending Query Result to described database client.
The database server of the present embodiment is for the technical scheme of embodiment of the method shown in execution graph 1, and it realizes principle and technique effect is similar, repeats no more herein.
Fig. 5 is the structural representation of database server embodiment bis-of the present invention, and as shown in Figure 5, the database server of the present embodiment is on the basis of structure shown in Fig. 4, and further, enquiry module 403, comprising:
Determining unit 403a, for according to described query argument, determines search index;
Sending module 404, specifically for:
Data in described output buffer are sent to described database client.
Further, copy cell 403b, specifically for:
According to described search index, determine at least two inquire addresses, wherein, the memory address in the corresponding tables of data of each inquire address;
According to each inquire address, from corresponding tables of data, search data, and copy the data that find to output buffer from each tables of data.
Further, receiver module 401, also for before receiving the inquiry request that database client sends: receive inquiry ID and query logic that database client sends, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query;
The database server of the present embodiment, can also comprise:
Accordingly, sending module 404, also for sending the metadata structure corresponding with the data of described buffer memory to described database client.
Further, cache module 405, specifically for:
According to described attribute description information, at least two tables of data are carried out to association;
Associated tables of data is carried out to buffer memory.
The database server of the present embodiment is for the technical scheme of embodiment of the method shown in execution graph 2, and it realizes principle and technique effect is similar, repeats no more herein.
Fig. 6 is the structural representation of database client embodiment of the present invention, and as shown in Figure 6, the database client of the present embodiment can comprise: sending module 601, receiver module 602, wherein:
Sending module 601, for sending inquiry request to database server, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Further, sending module 601, also for before sending inquiry request to database server: send inquiry ID and query logic to described database server, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query, so that described database server carries out buffer memory to data corresponding to described attribute description information, generate inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
The database server of the present embodiment is for the technical scheme of embodiment of the method shown in execution graph 3, and it realizes principle and technique effect is similar, repeats no more herein.
One of ordinary skill in the art will appreciate that: all or part of step that realizes above-mentioned each embodiment of the method can complete by the relevant hardware of programmed instruction.Aforesaid program can be stored in a computer read/write memory medium.This program, when carrying out, is carried out the step that comprises above-mentioned each embodiment of the method; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CDs.
Finally it should be noted that: above each embodiment, only in order to technical scheme of the present invention to be described, is not intended to limit; Although the present invention is had been described in detail with reference to aforementioned each embodiment, those of ordinary skill in the art is to be understood that: its technical scheme that still can record aforementioned each embodiment is modified, or some or all of technical characterictic is wherein equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution depart from the scope of various embodiments of the present invention technical scheme.
Claims (14)
1. a data base query method, is characterized in that, comprising:
Receive the inquiry request that database client sends, in described inquiry request, comprise inquiry sign ID and query argument;
According to described inquiry ID, determine pre-stored inquiry plan;
According to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
To described database client, send Query Result.
2. method according to claim 1, is characterized in that, described according to described query argument and definite inquiry plan, and executing data inquiry in the data of buffer memory in advance, comprising:
According to described query argument, determine search index;
According to described search index, determine inquire address, and the data that described inquire address place is preserved copy output buffer to;
Described to described database client transmission Query Result, comprising:
Data in described output buffer are sent to described database client.
3. method according to claim 2, is characterized in that, describedly according to described search index, determines inquire address, and the data that described inquire address place is preserved copy output buffer to, comprising:
According to described search index, determine at least two inquire addresses, wherein, the memory address in the corresponding tables of data of each inquire address;
According to each inquire address, from corresponding tables of data, search data, and copy the data that find to output buffer from each tables of data.
4. according to the method described in any one in claim 1～3, it is characterized in that, before the inquiry request that described reception database client sends, also comprise:
Receive inquiry ID and query logic that database client sends, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query;
The data that described attribute description information is corresponding are carried out to buffer memory;
Generate inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
To described database client, send the metadata structure corresponding with the data of described buffer memory.
5. method according to claim 4, is characterized in that, described data corresponding to described attribute description information is carried out to buffer memory, comprising:
According to described attribute description information, at least two tables of data are carried out to association;
Associated tables of data is carried out to buffer memory.
6. a data base query method, is characterized in that, comprising:
To database server, send inquiry request, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Receive the Query Result that described database server sends.
7. method according to claim 6, is characterized in that, described before database server transmission inquiry request, also comprises:
To described database server, send inquiry ID and query logic, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query, so that described database server carries out buffer memory to data corresponding to described attribute description information, generate inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
Receive metadata structure corresponding to the data with described buffer memory that described database server sends.
8. a database server, is characterized in that, comprising:
Receiver module, the inquiry request sending for receiving database client, comprises inquiry sign ID and query argument in described inquiry request;
Determination module, for determining pre-stored inquiry plan according to described inquiry ID;
Enquiry module, for according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Sending module, for sending Query Result to described database client.
9. database server according to claim 8, is characterized in that, described enquiry module, comprising:
Determining unit, for according to described query argument, determines search index;
Copy cell, for according to described search index, determines inquire address, and the data that described inquire address place is preserved copy output buffer to;
Described sending module, specifically for:
Data in described output buffer are sent to described database client.
10. database server according to claim 9, is characterized in that, described copy cell, specifically for:
According to described search index, determine at least two inquire addresses, wherein, the memory address in the corresponding tables of data of each inquire address;
According to each inquire address, from corresponding tables of data, search data, and copy the data that find to output buffer from each tables of data.
Database server in 11. according to Claim 8～10 described in any one, is characterized in that, described receiver module, also for before receiving the inquiry request of database client transmission:
Receive inquiry ID and query logic that database client sends, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query;
Described database server, also comprises:
Cache module, for data corresponding to described attribute description information are carried out to buffer memory, generates inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
Described sending module, also for sending the metadata structure corresponding with the data of described buffer memory to described database client.
12. database servers according to claim 11, is characterized in that, described cache module, specifically for:
According to described attribute description information, at least two tables of data are carried out to association;
Associated tables of data is carried out to buffer memory.
13. 1 kinds of database clients, is characterized in that, comprising:
Sending module, for sending inquiry request to database server, in described inquiry request, comprise inquiry sign ID and query argument, so that described database server is determined pre-stored inquiry plan according to described inquiry ID, and according to described query argument and definite inquiry plan, executing data inquiry in the data of buffer memory in advance;
Receiver module, the Query Result sending for receiving described database server.
14. database clients according to claim 13, is characterized in that, described sending module, also for before sending inquiry request to database server:
To described database server, send inquiry ID and query logic, in described query logic, comprise described inquiry ID the attribute description information of corresponding data query, so that described database server carries out buffer memory to data corresponding to described attribute description information, generate inquiry plan and the search index corresponding with the data of buffer memory, and described inquiry ID is carried out associated with described inquiry plan;
Described receiver module, metadata structure corresponding to the data with described buffer memory also sending for receiving described database server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410027522.0A CN103729471B (en) | 2014-01-21 | 2014-01-21 | Data base query method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410027522.0A CN103729471B (en) | 2014-01-21 | 2014-01-21 | Data base query method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103729471A true CN103729471A (en) | 2014-04-16 |
| CN103729471B CN103729471B (en) | 2017-03-08 |
Family
ID=50453545
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410027522.0A Active CN103729471B (en) | 2014-01-21 | 2014-01-21 | Data base query method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103729471B (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104866603A (en) * | 2015-06-01 | 2015-08-26 | 北京圆通慧达管理软件开发有限公司 | Calling method of metadata and metadata managing system |
| CN105224560A (en) * | 2014-06-20 | 2016-01-06 | 腾讯科技（北京）有限公司 | Data cached lookup method and device |
| CN105447009A (en) * | 2014-08-12 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Method and device for generating query strings |
| CN105760477A (en) * | 2016-02-15 | 2016-07-13 | 中国建设银行股份有限公司 | Data query method and system for multiple data sources and associated equipment therefore |
| CN105930496A (en) * | 2016-05-06 | 2016-09-07 | 深圳市永兴元科技有限公司 | Data query method and system |
| CN106528854A (en) * | 2016-11-28 | 2017-03-22 | 加和（北京）信息科技有限公司 | DMP querying method and device |
| CN106708838A (en) * | 2015-11-12 | 2017-05-24 | 华为技术有限公司 | Flow data query method and apparatus |
| CN106776638A (en) * | 2015-11-24 | 2017-05-31 | 大唐软件技术股份有限公司 | Database operation method and device |
| CN106844740A (en) * | 2017-02-14 | 2017-06-13 | 华南师范大学 | Data pre-head method based on memory object caching system |
| WO2017161989A1 (en) * | 2016-03-23 | 2017-09-28 | 中兴通讯股份有限公司 | Preprocessing method and device for distributed database and computer storage medium |
| CN107451252A (en) * | 2017-07-30 | 2017-12-08 | 深圳有麦科技有限公司 | Method for quickly querying and its system based on API |
| CN107517262A (en) * | 2017-08-31 | 2017-12-26 | 江西博瑞彤芸科技有限公司 | Business datum storage method |
| WO2018177060A1 (en) * | 2017-03-31 | 2018-10-04 | 华为技术有限公司 | Query optimization method and related device |
| CN109446386A (en) * | 2018-10-23 | 2019-03-08 | 中国银行股份有限公司 | A kind of data query method and device |
| CN110019559A (en) * | 2017-12-27 | 2019-07-16 | 航天信息股份有限公司 | A kind of data query method and system |
| CN110334114A (en) * | 2018-02-12 | 2019-10-15 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for inquiring data |
| CN111488382A (en) * | 2020-04-16 | 2020-08-04 | 北京思特奇信息技术股份有限公司 | Data calling method and system and electronic equipment |
| CN111506553A (en) * | 2019-01-31 | 2020-08-07 | 阿里巴巴集团控股有限公司 | Database function setting method and device |
| CN112035522A (en) * | 2020-07-16 | 2020-12-04 | 中科驭数（北京）科技有限公司 | Database data acquisition method and device |
| CN108090056B (en) * | 2016-11-21 | 2021-06-15 | 中兴通讯股份有限公司 | Data query method, device and system |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112784139A (en) * | 2021-01-13 | 2021-05-11 | 多点(深圳)数字科技有限公司 | Query method, query device, electronic equipment and computer readable medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110179014A1 (en) * | 2010-01-15 | 2011-07-21 | Ian Schechter | Managing data queries |
| CN102141990A (en) * | 2010-02-01 | 2011-08-03 | 阿里巴巴集团控股有限公司 | Searching method and device |
| CN102930054A (en) * | 2012-11-19 | 2013-02-13 | 北京奇虎科技有限公司 | Data search method and data search system |
| CN103064960A (en) * | 2012-12-31 | 2013-04-24 | 华为技术有限公司 | Method and equipment for database query |
| CN103226610A (en) * | 2013-05-07 | 2013-07-31 | 华为技术有限公司 | Method and device for querying database table |
| CN103324724A (en) * | 2013-06-26 | 2013-09-25 | 华为技术有限公司 | Method and device for processing data |
-
2014
- 2014-01-21 CN CN201410027522.0A patent/CN103729471B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110179014A1 (en) * | 2010-01-15 | 2011-07-21 | Ian Schechter | Managing data queries |
| CN102141990A (en) * | 2010-02-01 | 2011-08-03 | 阿里巴巴集团控股有限公司 | Searching method and device |
| CN102930054A (en) * | 2012-11-19 | 2013-02-13 | 北京奇虎科技有限公司 | Data search method and data search system |
| CN103064960A (en) * | 2012-12-31 | 2013-04-24 | 华为技术有限公司 | Method and equipment for database query |
| CN103226610A (en) * | 2013-05-07 | 2013-07-31 | 华为技术有限公司 | Method and device for querying database table |
| CN103324724A (en) * | 2013-06-26 | 2013-09-25 | 华为技术有限公司 | Method and device for processing data |
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224560A (en) * | 2014-06-20 | 2016-01-06 | 腾讯科技（北京）有限公司 | Data cached lookup method and device |
| CN105224560B (en) * | 2014-06-20 | 2019-12-06 | 腾讯科技（北京）有限公司 | Cache data searching method and device |
| CN105447009A (en) * | 2014-08-12 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Method and device for generating query strings |
| CN104866603A (en) * | 2015-06-01 | 2015-08-26 | 北京圆通慧达管理软件开发有限公司 | Calling method of metadata and metadata managing system |
| CN104866603B (en) * | 2015-06-01 | 2018-09-25 | 明算科技（北京）股份有限公司 | The call method and metadata management system of metadata |
| CN106708838A (en) * | 2015-11-12 | 2017-05-24 | 华为技术有限公司 | Flow data query method and apparatus |
| CN106776638A (en) * | 2015-11-24 | 2017-05-31 | 大唐软件技术股份有限公司 | Database operation method and device |
| CN105760477A (en) * | 2016-02-15 | 2016-07-13 | 中国建设银行股份有限公司 | Data query method and system for multiple data sources and associated equipment therefore |
| WO2017161989A1 (en) * | 2016-03-23 | 2017-09-28 | 中兴通讯股份有限公司 | Preprocessing method and device for distributed database and computer storage medium |
| CN107229628A (en) * | 2016-03-23 | 2017-10-03 | 中兴通讯股份有限公司 | The method and device of distributed data base pretreatment |
| CN107229628B (en) * | 2016-03-23 | 2022-02-01 | 金篆信科有限责任公司 | Distributed database preprocessing method and device |
| CN105930496A (en) * | 2016-05-06 | 2016-09-07 | 深圳市永兴元科技有限公司 | Data query method and system |
| CN108090056B (en) * | 2016-11-21 | 2021-06-15 | 中兴通讯股份有限公司 | Data query method, device and system |
| CN106528854A (en) * | 2016-11-28 | 2017-03-22 | 加和（北京）信息科技有限公司 | DMP querying method and device |
| CN106844740A (en) * | 2017-02-14 | 2017-06-13 | 华南师范大学 | Data pre-head method based on memory object caching system |
| WO2018177060A1 (en) * | 2017-03-31 | 2018-10-04 | 华为技术有限公司 | Query optimization method and related device |
| CN107451252A (en) * | 2017-07-30 | 2017-12-08 | 深圳有麦科技有限公司 | Method for quickly querying and its system based on API |
| CN107517262A (en) * | 2017-08-31 | 2017-12-26 | 江西博瑞彤芸科技有限公司 | Business datum storage method |
| CN110019559A (en) * | 2017-12-27 | 2019-07-16 | 航天信息股份有限公司 | A kind of data query method and system |
| CN110334114A (en) * | 2018-02-12 | 2019-10-15 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for inquiring data |
| CN109446386B (en) * | 2018-10-23 | 2020-10-27 | 中国银行股份有限公司 | Data query method and device |
| CN109446386A (en) * | 2018-10-23 | 2019-03-08 | 中国银行股份有限公司 | A kind of data query method and device |
| CN111506553A (en) * | 2019-01-31 | 2020-08-07 | 阿里巴巴集团控股有限公司 | Database function setting method and device |
| CN111506553B (en) * | 2019-01-31 | 2023-07-04 | 阿里巴巴集团控股有限公司 | Function setting method and device for database |
| CN111488382A (en) * | 2020-04-16 | 2020-08-04 | 北京思特奇信息技术股份有限公司 | Data calling method and system and electronic equipment |
| CN112035522A (en) * | 2020-07-16 | 2020-12-04 | 中科驭数（北京）科技有限公司 | Database data acquisition method and device |
| CN112035522B (en) * | 2020-07-16 | 2021-09-07 | 中科驭数（北京）科技有限公司 | Database data acquisition method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103729471B (en) | 2017-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103729471A (en) | Method and device for database query | |
| CN101727465B (en) | Methods for establishing and inquiring index of distributed column storage database, device and system thereof | |
| US9996565B2 (en) | Managing an index of a table of a database | |
| US9020882B2 (en) | Database hosting middleware dimensional transforms | |
| US9460192B2 (en) | Management of a database system | |
| US10242051B2 (en) | Efficient multi-tenant spatial and relational indexing | |
| US9183267B2 (en) | Linked databases | |
| US9483515B2 (en) | Managing a table of a database | |
| CN104102710A (en) | Massive data query method | |
| US20090043726A1 (en) | Spatial join in a parallel database management system | |
| US9229960B2 (en) | Database management delete efficiency | |
| CN106708996A (en) | Method and system for full text search of relational database | |
| US20170154073A1 (en) | System and method for retrieving data | |
| US10496645B1 (en) | System and method for analysis of a database proxy | |
| US11422994B2 (en) | Adaptive query processor for query systems with limited capabilities | |
| CN103823846A (en) | Method for storing and querying big data on basis of graph theories | |
| CN107423037B (en) | Application program interface positioning method and device | |
| US20150310039A1 (en) | System and method for geo-location data type searching in an on demand environment | |
| CN103353901A (en) | Orderly table data management method and system based on Hadoop distributed file system (HDFS) | |
| US9069681B1 (en) | Real-time log joining on a continuous stream of events that are approximately ordered | |
| CN113268502A (en) | Method and equipment for providing information | |
| CN108874950A (en) | A kind of distributed data storage method and device based on ER relationship | |
| CN107644017A (en) | The querying method and device of journal file | |
| CN111400301B (en) | Data query method, device and equipment | |
| US10990588B2 (en) | Optimizing continuous query operations in an in memory data grid (IMDG) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200214 Address after: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee after: HUAWEI TECHNOLOGIES Co.,Ltd. Address before: 210012 Ande Gate No. 94, Yuhuatai District, Jiangsu, Nanjing Patentee before: Huawei Technologies Co.,Ltd. |
|
| TR01 | Transfer of patent right |