SYSTEMS AND METHODS FOR CANCELLING A QUERY

• US 20140280332A1
• Filed: 10/23/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Looker Data Sciences, Inc. (Alphabet Inc.)
• Inventors: Porterfield, Benjamin
• Granted Patent: US 10,191,984 B2
• Time in Patent Office: Days
• US Class Current: 707/770
• CPC Class Codes: G06F 16/2425 Iterative querying; Query formulation based on the results of a preceding query
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques

Abstract

Systems and methods for querying a database are disclosed. A server computing device includes a processor and a memory storing instructions that, when executed by the processor, cause the server computing device to: receive a query input from a client device over a network connection; establish a non-blocking socket between the client computing device and the server computing device; generate a database query based on the query input; cause the database query to begin executing against one or more databases; perform a read request on the non-blocking socket; receive a code in response to the read request on the non-blocking socket; determine whether the network connection exists between the client device and the server device based on the received code; and cause the database query to be cancelled when the server determines that the network connection does not exist between the client device and the server device.

Claims

1. A method for querying a database, comprising:

receiving, by a server computing device, a query input from a client device over a network connection;

establishing a non-blocking socket between the client computing device and the server computing device;

generating a database query based on the query input;

causing the database query to begin executing against one or more databases;

performing, by the server computing device, a read request on the non-blocking socket;

receiving a code in response to the read request on the non-blocking socket;

determining whether the network connection exists between the client device and the server device based on the received code; and

causing the database query to be cancelled when the server determines that the network connection does not exist between the client device and the server device.

2. The method according to claim 1, wherein one or more databases are relational databases and the query is an SQL (Structured Query Language) query.

3. The method according to claim 1, wherein causing the database query to be cancelled comprises causing a second database query to begin executing against the one or more databases.

4. The method according to claim 1, wherein a one-to-one mapping exists between each non-blocking socket and a corresponding query, and wherein a list is maintained of each non-blocking socket-query mapping.

5. The method according to claim 4, further comprising periodically performing the read request on each non-blocking socket included in the list.

6. The method according to claim 1, wherein the code indicates that the client computing device at the other end of the non-blocking socket from the server computing device is connected over the network connection.

7. The method according to claim 6, wherein the code comprises one or more of an “

EAGAIN”

or an “

EWOULDBLOCK”

message.

8. A server computing device for querying a database, comprising:

a processor; and

a memory storing instructions that, when executed by the processor, cause the server computing device to;

receive a query input from a client device over a network connection;

establish a non-blocking socket between the client computing device and the server computing device;

generate a database query based on the query input;

cause the database query to begin executing against one or more databases;

perform a read request on the non-blocking socket;

receive a code in response to the read request on the non-blocking socket;

determine whether the network connection exists between the client device and the server device based on the received code; and

cause the database query to be cancelled when the server determines that the network connection does not exist between the client device and the server device.

9. The server computing device according to claim 8, wherein one or more databases are relational databases and the query is an SQL (Structured Query Language) query.

10. The server computing device according to claim 8, wherein causing the database query to be cancelled comprises causing a second database query to begin executing against the one or more databases.

11. The server computing device according to claim 8, wherein a one-to-one mapping exists between each non-blocking socket and a corresponding query, and wherein a list is maintained of each non-blocking socket-query mapping.

12. The server computing device according to claim 11, further comprising periodically performing the read request on each non-blocking socket included in the list.

13. The server computing device according to claim 8, wherein the code indicates that the client computing device at the other end of the non-blocking socket from the server computing device is connected over the network connection.

14. The server computing device according to claim 13, wherein the code comprises one or more of an “

EAGAIN”

or an “

EWOULDBLOCK”

message.

15. A client computing device for querying a database, comprising:

a processor; and

a memory storing instructions that, when executed by the processor, cause the client computing device to;

transmit a query input to a server computing device over a network connection, wherein a non-blocking socket is established between the client computing device and the server computing device, and wherein a database query is generated and executed against one or more database based on the query input;

receive a read request from the server computing device on the non-blocking socket; and

transmit a code to the server computing device in response to the read request on the non-blocking socket, wherein the code allows the server computing device to determine whether the network connection still exists between the client device and the server computing device based on the received code, and wherein the server computing device is able to cause the database query to be cancelled when the server computing device determines that the network connection does not exist between the client device and the server computing device.

16. The client computing device according to claim 15, wherein one or more databases are relational databases and the query is an SQL (Structured Query Language) query.

17. The client computing device according to claim 15, wherein a one-to-one mapping exists between the non-blocking socket and the query, and wherein a list is maintained of each non-blocking socket-query mapping.

18. The client computing device according to claim 15, wherein the read requests are periodically received from the server computing device.

19. The client computing device according to claim 15, wherein the code indicates that the client computing device is connected over the network connection.

20. The client computing device according to claim 15, wherein the code comprises one or more of an “

EAGAIN”

or an “

EWOULDBLOCK”

message.