SERVER SUPPORTING A CONSISTENT CLIENT-SIDE CACHE

• US 20080098041A1
• Filed: 10/22/2007
• Published: 04/24/2008
• Est. Priority Date: 10/20/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: CHIDAMBARAN, Lakshminarayanan, LAHIRI, Tirthankar, BASTAWALA, Mehul, KRISHNASWAMY, Srinath, SINHA, Bipul, LOAIZA, Juan, VEMURI, Srinivas
• Granted Patent: US 10,296,629 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24539 using cached or materialised query results
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

A method, system, and computer program product is disclosed for interacting with a client supported by a client-side cache. Embodiments of a method, a system, and a computer program product are disclosed that retrieve a first snapshot, indicating a state of the database after a last database request by the client, associated with the client, determine any number of invalid cached results for the client based on the first snapshot, and transmit the any number of invalid cached results and a second snapshot, an update for the first snapshot.

Claims

1. A method for a database server to interact with a client supported by a client-side cache, comprising:

retrieving a first snapshot associated with the client, wherein the first snapshot indicates a state of the database after a last database request by the client;

determining any number of invalid cached results for the client based on the first snapshot; and

transmitting the any number of invalid cached results and a second snapshot, wherein the second snapshot is an update for the first snapshot.

2. The method of claim 1, further comprising:

receiving a database server request from the client, wherein the database server request includes the first snapshot; and

creating the second snapshot, wherein the second snapshot is a state of the database upon processing of the database server request.

3. The method of claim 1, wherein the any number of invalid cached results further comprises either cached result identifiers or cached results that relate to database transactions that occurred between the first snapshot and the second snapshot.

4. The method of claim 1, further comprising:

performing garbage collection after abnormal termination of the client.

5. The method of claim 1, wherein the any number of invalid cached results further comprises either cached results or cached results identifiers for a client session that relate to uncommitted database changes made by the client with the client session.

6. The method of claim 2, further comprising:

requesting a database execute a query from the database server request;

determining if the query is cacheworthy;

registering the query with a database change notification module if the query is cacheworthy; and

transmitting a query result to the client.

7. The method of claim 6, wherein the query accesses one or more tables to form the query result.

8. A method for a database interface supporting a client cache, comprising:

requesting a database server service a database request from a client;

indicating to the database server that a first snapshot is associated with the client, wherein the first snapshot is a state of the database after a last database request by the client; and

receiving any number of cache invalidations and a second snapshot from the database server, wherein the second snapshot is an update for the first snapshot.

9. The method of claim 8, further comprising:

receiving query results for a query in the database request; and

receiving one or more keys for caching the query results in the client cache.

10. A database management system that interacts with a client supported by a client-side cache, comprising:

a database server for retrieving a first snapshot associated with the client, wherein the first snapshot indicates a state of the database after a last database request by the client;

a database change notification module for determining any number of invalid cached results for the client based on the first snapshot; and

a database interface for transmitting the any number of invalid cached results and a second snapshot, wherein the second snapshot is an update for the first snapshot.