Automatically caching data is useful when you do not want to rebuild the cache for each query. When you query data for the first time, the provider automatically initializes and builds a cache in the background. When AutoCache = true, the provider uses the cache for subsequent query executions, resulting in faster response times.

Configuring Automatic Caching

Caching the Timesheets Table

The following example caches the Timesheets table in the file specified by the CacheLocation property of the connection string.

C#

String connectionString = "Cache Location=C:\\cache.db;AutoCache=true;OAuthClientId=myclientid;OAuthClientSecret=myclientsecret;InitiateOAuth=GETANDREFRESH;CallbackUrl=http://localhost:33333;";
using (QuickBooksTimeConnection connection = new QuickBooksTimeConnection(connectionString)) {
  QuickBooksTimeCommand cmd = new QuickBooksTimeCommand("SELECT Id, JobcodeId FROM Timesheets WHERE JobCodeType = 'regular'", connection);
  QuickBooksTimeDataReader rdr = cmd.ExecuteReader();
  while (rdr.Read()) {
    Console.WriteLine("Read and cached the row with Id " + rdr["Id"]);
  }
}

VB.NET

Dim connectionString As [String] = "Cache Location=C:\\cache.db;AutoCache=true;OAuthClientId=myclientid;OAuthClientSecret=myclientsecret;InitiateOAuth=GETANDREFRESH;CallbackUrl=http://localhost:33333;"
Using connection As New QuickBooksTimeConnection(connectionString)
  Dim cmd As New QuickBooksTimeCommand("SELECT Id, JobcodeId FROM Timesheets WHERE JobCodeType = 'regular'", connection)
  Dim rdr As QuickBooksTimeDataReader = cmd.ExecuteReader()
  While rdr.Read()
	  Console.WriteLine("Read and cached the row with Id " + rdr("Id"))
  End While
End Using

Common Use Case

A common use for automatically caching data is to improve driver performance when making repeated requests to a live data source, such as building a report or creating a visualization. With auto caching enabled, repeated requests to the same data may be executed in a short period of time, but within an allowable tolerance (CacheTolerance) of what is considered "live" data.