From 810d5015dd535098cef3f7c16d997374d0d431ac Mon Sep 17 00:00:00 2001 From: Derek Allard Date: Sun, 15 Jun 2008 17:23:48 +0000 Subject: userguide typo fix --- user_guide/database/active_record.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'user_guide/database') diff --git a/user_guide/database/active_record.html b/user_guide/database/active_record.html index 1a3c9b6e2..aaee21e97 100644 --- a/user_guide/database/active_record.html +++ b/user_guide/database/active_record.html @@ -699,7 +699,7 @@ $query = $this->db->get();

 Active Record Caching

While not "true" caching, Active Record enables you to save (or "cache") certain parts of your queries for reuse later. Normally, when an Active Record call is completed, all stored information is reset for the next call. With caching, you can prevent this reset, and reuse information easily.

-

Cached calls are cumulative.  If you makes 2 cached select() calls, and then 2 uncached select() calls, this will result in 4 select() calls. There are three Caching functions available:

+

Cached calls are cumulative.  If you make 2 cached select() calls, and then 2 uncached select() calls, this will result in 4 select() calls. There are three Caching functions available:

$this->db->start_cache()

This function must be called to begin caching. All Active Record queries of the correct type (see below for supported queries) are stored for later use.

$this->db->stop_cache()

-- cgit v1.2.3-24-g4f1b