Skip to main content

Built-in Row Cache

  • 3 minutes to read

The ASPxGridView control has a built-in cache that stores visible row data and allows the control to avoid additional data binding.

Row Cache Life Cycle

ASPxGridView copies field values of visible and invisible columns to an internal data collection contained in a hidden field. A page sends the hidden field values to the server with postback and callback data. On the server, this data is deserialized.

When ASPxGridView requires row data, the control attempts to load that data from the row cache. If all required rows are available in the cache, ASPxGridView does not send a query to the database. Since the row cache contains only visible row data, this mechanism is effective exclusively if a row list on the current page does not change. For example, the row cache is particularly useful in the following scenarios when:

  • A user selects, focuses a row, or moves a column on the current page.
  • Another page control initiates a page request. In this case, ASPxGridView data does not change unless ASPxGridView is modified on the server side during this request.

Sort, filter, and page operations cause new rows to appear on a page. Row cache does not have data for new rows and ASPxGridView sends a query to the database to obtain necessary data.

Methods That Can Force Data Binding

GetRowValues(Int32, String[]) | Find...TemplateControl
These methods return row values. When you call these methods, ASPxGridView searches for a value in the row cache. If the required row data is found, data binding does not occur. ASPxGridView binds to a data source if the row cache is disabled or has no required data.
GetRow(Int32) | GetDataRow(Int32)
These methods return a row data object rather than row values. ASPxGridView does not store data objects in the row cache, therefore, these methods cause data binding even if the row cache contains required data.

Disable Row Cache

Set the EnableRowsCache property to false to disable the row cache. This option can be useful in the following cases:

How to Store Complex Objects in Cache

If you bind a grid to an XPO or custom objects that use a referenced association, the control also tries to cache references. The caching operation is similar to the ToString method. Serialization of a custom object copies data row values from a data source into an internal data collection. However, object deserialization (restoration from string to object) raises an exception:

"TypeConverter cannot convert from System.String"

You can resolve the issue in the following ways: